On Sat, 30 May 2009 22:14:32 +0100, Matthew Toseland wrote:
On Sunday 10 May 2009 15:51:39 Dennis Nezic wrote:
On Wed, 15 Apr 2009 12:58:48 -0400, Dennis Nezic wrote:
I have seen a couple times my node stall due to exceeding the
thread limit, caused by an absurd 333 HTTP socket
On Sunday 10 May 2009 15:51:39 Dennis Nezic wrote:
On Wed, 15 Apr 2009 12:58:48 -0400, Dennis Nezic wrote:
I have seen a couple times my node stall due to exceeding the thread
limit, caused by an absurd 333 HTTP socket handlers (86.7% of thread
usage). (My node's thread limit is 300).
On Wed, 15 Apr 2009 12:58:48 -0400, Dennis Nezic wrote:
> I have seen a couple times my node stall due to exceeding the thread
> limit, caused by an absurd 333 "HTTP socket handlers" (86.7% of thread
> usage). (My node's thread limit is 300).
>
> I believe this is caused by my browser (dillo)
On Wed, 15 Apr 2009 12:58:48 -0400, Dennis Nezic wrote:
I have seen a couple times my node stall due to exceeding the thread
limit, caused by an absurd 333 HTTP socket handlers (86.7% of thread
usage). (My node's thread limit is 300).
I believe this is caused by my browser (dillo) making too
I have seen a couple times my node stall due to exceeding the thread
limit, caused by an absurd 333 "HTTP socket handlers" (86.7% of thread
usage). (My node's thread limit is 300).
I believe this is caused by my browser (dillo) making too many
connections to fproxy. But, nevertheless, shouldn't
I have seen a couple times my node stall due to exceeding the thread
limit, caused by an absurd 333 HTTP socket handlers (86.7% of thread
usage). (My node's thread limit is 300).
I believe this is caused by my browser (dillo) making too many
connections to fproxy. But, nevertheless, shouldn't
