Oskar, are we clearing the entries in the memory datastore when we clear
them from the disk too?  (I don't know how that works in current Fred).

On Fri, 29 Dec 2000, Mark J. Roberts wrote:

> On Wed, 27 Dec 2000, Benjamin Coates wrote:
> 
> > >From "Mark J. Roberts" <[EMAIL PROTECTED]>
> > >On Wed, 27 Dec 2000, Mark J. Roberts wrote:
> > >
> > >Well, that's all working great for me now. The only problem is that FProxy
> > >leaks memory so terribly that it would be impossible to surf Freenet for
> > >more than 10 minutes without swapping and thrashing.
> > >
> > >  PID USER     PRI  NI  SIZE  RSS SHARE STAT  LIB %CPU %MEM   TIME COMMAND
> > >  444 root       9   0 87460  73M   380 S       0  0.0 59.9   0:00 java
> > >
> > >(I have 128 megs of RAM!)
> > >
> > >This is fucking unbelievable. I want to kill somebody. At first I thought
> > >it was my fault, and after fooling around with my code for an hour, I
> > >checked out a fresh, unaltered tree -- and it was EXACTLY THE SAME!
> > >(Actually, Mr. Bad's SSK subspace, with about 10-15 images, leaked about
> > >the same as or a little more than my hashtable in a mapspace with 35
> > >images (full shift-key reload for both). This is strong evidence in favor
> > >of MSKs.)
> > >
> > >Is this the fault of SimplifiedClient and ProxyClient? Brandon, do you
> > >have any idea what's causing this? Should someone who knows a lot about
> > >memory and Java rewrite SimplifiedClient or something? Or is this a bigger
> > >problem?
> > >
> > >
> > >--
> > >Mark Roberts
> > >[EMAIL PROTECTED]
> > >
> > 
> > I'm not sure this is fproxy...  My non-fproxy node likes to settle in at 
> > around 75MB on my system.  It also likes to go into a state where it uses all 
> > free cpu cycles (although it continues to run).  Anyone else getting these 
> > sort of things?
> 
> I let my node do its typical noding for a while and sure enough it was
> eating 63M of memory. Whatever's doing this, it happens during normal node
> operation as well as FProxy use.
> 
> > More importatntly, is there a way of determining what is using all this 
> > memory?  A java heap examiner or somesuch?
> 
> We must be doing something that's short-circuiting Java GC. Fred starts at
> about 11M, grows to 18M after it reads my store file, and grows from
> there.
> 
> 
> -- 
> Mark Roberts
> [EMAIL PROTECTED]
> 
> 
> _______________________________________________
> Freenet-dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/mailman/listinfo/freenet-dev
> 
> 


_______________________________________________
Freenet-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to