Puhh.. latest unstable code is soooooooooooo much more CPU friendly.. it is like it was at about 6194 which was about the point where the latest unstable started permanently using up 100% CPU. Unfortunately I cannot tell the exact build but it certainly was around there...
Another difference (possibly because of the decreased CPU useage) is that my node finally are able to use its allowed 100kByte/s again.. last week or two it has managed to trickle out a maximum of 10kByte/s. /N ----- Original Message ----- From: "Zlatin Balevsky" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, September 23, 2003 3:58 AM Subject: [freenet-dev] high cpu - ngr.references() > I had a ~5 minute 100% cpu spike with latest cvs (which includes > lostlogic's blacklist patches). A stack dump gives tons of threads > (including wsl) waiting to lock a lru in ocm , and the thread holding it > waiting to lock a hashtable in ngr.references(). Nothing visibly holds > that monitor. > > > ---------------------------------------------------------------------------- ---- > _______________________________________________ > Devl mailing list > [EMAIL PROTECTED] > http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
