On Sat, Sep 06, 2003 at 09:54:26PM -0400, Zlatin Balevsky wrote: > Seems like the high cpu usage is due mainly to heavy churn of new > connections being opened on popular nodes. Eventually a feedback loop > occurs: new connections are being opened to reject queries due to bw > limits, and those negotiations in turn take up the bandwith causing more > QRs. > > My node receives around 60000 qph. With the default limit of 512 > connections between 200 and 300 new connections are opened every minute > (half of them through the ConnectionOpener). I increased my limit to > 1024 connections and for an hour and a half uptime only 800 were used up > (rtSize=64). The ratio of new connections had dropped to ~70 per > minute, and cpu usage had therefore gone down significantly. > > So... it may be time to do the buffer pooling. It will solve two > problems with one bullet - the high memory requirements and the high cpu > usage (as it will allow nodes to have higher number of connections). > The default of 512 should stay on *nix systems where root privileges are > required to have more than 1k descriptors. On windoze systems there is > no limit on the number of sockets, so a more liberal limit can be set.
Maybe so. The single queue per peer refactoring comes first though. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
pgp00000.pgp
Description: PGP signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
