Tor client performance (was Re: URGENT: patch needed ASAP for authority bug)

[Mike Perry]

Thus spake Richard Johnson (rdump at river.com):

> Additional problems uncovered in this process:
>  o  torrc write failure caused tor crash [2] on [1].
>  o  DirPort was not listening in practice despite its config line still
>     being in torrc after the write failure, and despite it being logged
>     as starting.
> 
> I've now run tor for 6 hours since, with no repeat of "Error creating
> network socket: Too many open files" so far.  It indeed looks like it is
> directory mirror connections coming in at a high rate all of a sudden,
> thereby running the account out of its allocation of file
> descriptors/sockets.

Things could also have gotten better for you because your node may
have lost the Guard flag, which is another possible pain point. A
crashing/frequently restarted relay may lose its Guard flag, which
would also drastically reduce its load in terms of the number of
connections.

Can you please provide us with your relay name, or paste its list of
*blue* Consensus column flags from:
http://metrics.torproject.org/consensus-health.html



-- 
Mike Perry
Mad Computer Scientist
fscked.org evil labs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20100421/ec2e1197/attachment.pgp>