On Thu, Feb 06, 2003 at 04:00:38PM -0700, Jack D. Ripper wrote:
On Thursday 06 February 2003 01:32 pm, Jack D.Ripper wrote:
On Thursday 06 February 2003 12:35 pm, Matthew Toseland wrote:
I already had maximumThreads set at 50 (sorry I didn't mention that,
there's so many configuration variables that I have fiddled with trying to
tune this thing that I forget what I've done to what!). When Frost
overloaded my node, it had *HUNDREDS* of threads open, though. How could
that be?! (My node is running Mandrake 9.0 Linux, stock 2.4.19 kernel).
I will add the defaultResetProbability line and see if that helps. Thanks,
Hmm, didn't help. maximumThreads set at 50, defaultResetProbability set at
0.01, fired up Frost again, and here we go:
Which Frost? The old one or the new (with FEC splitfile support) one?
The new one seems reasonably well-behaved.
(from Environment screen)
Pooled Thread Consumers
Class Threads used
Checkpoint: Fetching ARK freenet:SSK 1
freenet.Message: ClientGet 11
Checkpoint: Native Filesystem Directory checkpoint 1
Why do I have 69 Connectionjob threads when I have maximumThreads set at 50?
It seems to me that this beast is initiating and accepting connections after
it hits that limit! At the very least it should not be initiating connections
after we hit maximumThreads, or assigning sockets to connections threads
after we hit maximumThreads, right? Otherwise, what use is maximumThreads?!
Worse, this is actually *understimating* the number of threads outstanding.
ps -ax shows approximately 300 Java threads actually running!
Something isn't getting throttled right. What now?
Build Number 554 CVS Revision 184.108.40.206
Mandrake 9.0 Linux stock 2.4.19 kernel
Jack D. Ripper, NORAD HQ, Cheyenne Mountain, CO [EMAIL PROTECTED]
support mailing list
[EMAIL PROTECTED][EMAIL PROTECTED]
Full time freenet hacker.
Freenet Distribution Node (temporary) at http://amphibian.dyndns.org:8889/3arPAuj7w-c/
Description: PGP signature