On Tue, Nov 04, 2003 at 09:10:08AM -0500, Daves Lists wrote: > Always active jobs. Here's what I generally look like once the node has been > up and running a few hours. I tried bringing the threads up to support the > connections but that always seemed to cause the node to slow down and then I > would reject on routing time or messagesendtime. > > Total pooled threads 455 > Available pooled threads 189 > Pooled threads in use 266 > > Pooled Thread Consumers > > Class Threads used > Checkpoint: Connection opener 28 > freenet.interfaces.LocalNIOInterface$ConnectionShell 1 > freenet.interfaces.PublicNIOInterface$ConnectionShell 173 > freenet.node.states.data.DataStateInitiator 55 > freenet.node.states.data.TrailerWriteCallbackMessage:true:true 9
Oooh, interesting. If the reason for QRing is too many active jobs, and the reason for that is connections... then rather than NIO'ing connections, the solution is to implement multiplexing. But I need to know whether this is characteristic. > > Dave -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
