On Thu, 16 Apr 2009, Dan Langille wrote: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > 1264 root 15 0 2007m 804m 1408 S 0.0 78.6 2:49.23 bacula-dir > > > > http://filepile.dicp.de/bacula-dir-memory.png > > Could this be the spooled attributes taking up memory? > > Is the value increasing as time goes on?
Might be attributes. But the jobs are all blocked waiting for either Max Storage Jobs or similar. Even though there are 230 jobs waiting in the queue, no new attributes should be spooled, right? So why is the committed memory currently at 2.5G RAM? regards, andreas ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users