Roger Hayter ([EMAIL PROTECTED]) wrote: > If pushed I could try and give detail on this, but most notably this > seems to be the most unpredictable build I have tried yet. It sometimes > drifts into doing very little, sometimes dies of excessive threads, and > sometimes just uses excess CPU time while not actually serving any > incoming requests, and serving local requests, and fproxy pages, > exceedingly slowly.
How is your node doing on memory usage? My 535 node seems to be leaking memory: pegasus:~$ ps auxw | grep freenet freenet 31085 5.5 0.0 189972 194452 p4- SN Wed01PM 98:04.43 /usr/local/kaffe/jre/bin/kaffe-bin -mx 224M freenet.node.Main freenet 31085 9.0 0.0 190996 195792 p4- SN Wed01PM 99:52.07 /usr/local/kaffe/jre/bin/kaffe-bin -mx 224M freenet.node.Main When the memory usage gets up to the limit that I assigned, the node will start to report OutOfMemoryError in the freenet.log and won't respond to fproxy requests until I restart it. I'm thinking about going back to build 533, but I can't prove that 533 is actually better. -- Greg Wooledge | "Truth belongs to everybody." [EMAIL PROTECTED] | - The Red Hot Chili Peppers http://wooledge.org/~greg/ |
msg02139/pgp00000.pgp
Description: PGP signature
