jonathan.i.yu at gmail.com
Mon Mar 17 13:41:59 UTC 2008
I am by no means an expert, but I don't think that this is the case.
Tor uses libevent, which will automatically select the best I/O
multiplexing system; this is probably anything but select() on your
system. Hopefully it's an event-based system like kqueue (BSD) or
realtime signals (Linux).
There will probably be logs in the Tor console if this is indeed the
case.... My first advice would be to take a look there. It may be
because your system has run out of memory and begun swapping to disk?
Not knowing the characteristics of your installation, it is difficult
I hope this helps, but if you want more complete advice I suggest you
submit information such as your system specifications, operating
system, configuration, and so forth.
On Mon, Mar 17, 2008 at 8:33 AM, Toby Douglass
<toby.douglass at 45mercystreet.com> wrote:
> I installed Tor on the weekend. I've noticed that when I have a large
> number of concurrent sockets open - say, browsing with half a dozen tabs
> or more - everything actually *stops*. I have to stop loading all the
> tabs, and then go back to doing them, say, one by one.
> Would I be right in saying this is because select() is getting overwhelmed?
More information about the tor-dev