[freenet-dev] BDB uses far more memory than it's supposed to; ideas?

[Matthew Toseland]

On Fri, Feb 02, 2007 at 01:29:54AM +0000, Bob Ham wrote:
> On Thu, 2007-02-01 at 18:44 +0000, Matthew Toseland wrote:
> > On Tue, Jan 30, 2007 at 09:39:05PM +0000, Bob Ham wrote:
> 
> > > It's clear to see that the configured limits are wholly ignored, and by
> > > significant percentages.  This is a major problem. 
> > 
> > On the contrary this is utterly irrelevant.
> 
> Not when my named gets killed.
> 
> > It is Sun's problem, not our
> > problem
> 
> Yes, but the limits are still being wholly ignored.  Which JVM would you
> suggest running fred with that will respect configured memory limits?
> 
> > What was the limit set to?
> 
> 196 MB
> 
> > What was the usage reported in the log file
> > (Memory in use: <blah> - only enabled with minor logging)?
> 
> Which log file; wrapper log or fred log?  The statistics for the "java
> memory allocated" and "java memory used" come straight off of the
> statistics page of the web interface.

And they exceeded 192MB? I have never seen this; what JVM?
> 
> > What was the
> > reported RSS?
> 
> What you see plotted.
> 
> > How much memory do you actually have (and swap)?
> 
> 512 MB physical, 478 MB swap
> 
> > > Even disregarding the
> > > database, fred's memory footprint is massive. 
> > 
> > Negative. I was running it with a maximum memory setting of 100MB, and
> > 54MB+ of that was used by the database. If the database had respected
> > the configured setting of 20MB, that would be a grand total of 64MB.
> > Which IMHO is very reasonable.
> 
> Here is a plot with a maximum setting of 64MB, taken a couple of weeks
> ago:
> 
>   http://teasel.6gnip.net/~rah/freenet-threads-2007-02-02-01:17:33.png
> 
> I've put it up here as well in case you have problems:
> 
>   http://pkl.net/~node/freenet-threads-2007-02-02-01:17:33.png

This is all taken from the web interface? Or are you using some external
tool? I assume "Count" is in megabytes?
> 
> As you can see, there are quite a few "wrapper rstrt" labels; meaning
> the wrapper has restarted the node.  The reason in these instances
> appear to be "OOM" messages.  I'll set my memory limit to 100MB and see
> what kind of stability results.
> 
> Bob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://emu.freenetproject.org/pipermail/devl/attachments/20070203/0c61d704/attachment.pgp