Hi,
I'm running the node 'communicator' and upgraded from 0.1.1.25 to 0.1.2.14
last week. Since then I've been wondering why my node didn't want to
deliver the directory listing anymore - even at times when the used
bandwidth was _way_ below the configured maximum bandwidth of 1MB/s
("HTTP/1.0 503 Directory busy, try again later").
After some experimenting I think I stumbled upon the answer: it seems to me
that tor tries to deliver the whole directory listing (roughly 2.6MB) in
one second. At least that seems to be the needed bandwidth tor is
calculating for that transaction. Thus you need to have configured a
BandwidthRate or BandwidthBurst of at least 2.6 MB/s to be able to deliver
directory listings (even more as the network of tor nodes grows).
Is this working as intended? If it is, then please add a hint about this to
the documentation. But in my opinion it would be sufficient to deliver the
directory listing in 5 or 10 seconds, reducing the needed bandwidth
accordingly.
Btw: would it be possible to (g)zip the directory listing before delivering
it? That would cut the file size down about 50%.
Cheers, Stephan
Attachment:
pgpD9XQA61097.pgp
Description: PGP signature