On Sun, 2003-09-21 at 16:39, Benny Amorsen wrote: > On 2003-09-21 at 21:40, Edward J. Huff wrote: > > > We are trying to keep bandwidth use constant and as high as > > we are allowed, to keep thread usage down, and to keep > > routing time down.
Of course, I meant as a proxy for CPU time, or for the user's computer to be responsive enough that he won't shut down the node when he needs to get some work done. I also noticed that there are two different messages which appear: node is queryrejecting all requests, vs. node is rejecting all connections and requests. So there is a second knob, the rate of accepting new connections. Perhaps one could also use the total maximum number of connections as a knob. > [...] > > Oh by the way, RoutingTime is a pretty bad estimator of CPU load. But > that problem is insignificant next to the others. > I thought of a way to accept CPU load information: let the web server to accept the load as a parameter on a URL, and write a Perl script which finds the load and sends in the GET request. Or maybe a simpler protocol: listen on a port, accept a connection, and read load numbers from it. Then you don't have to do Java to C interfaces and use a different C implementation for each OS. -- Edward J. Huff <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
