On Thursday 29 April 2004 10:10 am, Jensen, Mark P. wrote:
Bruce, as long as that is the amount of memory the programs should use, I guess that means this is not a minor bug in your software. In my case, it's a user that was being miserly with hard drive space.
That's the conlcusion I came to as well. On my computer (linux, SuSE 9.0, KDE 3.2, KSystemGuard for looking at resources) I find that each program uses something in the neighborhood of 55 M of RAM and has about an additional 200 M of virtual memory allocated to it. I use a proram called GKrellm to monitor the use of swap and I find that, after 3 days of work, I have at some point used about 100 M of the swap space -- that is, only about 25% of what might have been used by both programs. So it would seem that the solution is to make sure that sufficient virtual memory is allocated. B -- Bruce Ravel ----------------------------------- ravel@phys.washington.edu Code 6134, Building 3, Room 405 Naval Research Laboratory phone: (1) 202 767 2268 Washington DC 20375, USA fax: (1) 202 767 4642 NRL Synchrotron Radiation Consortium (NRL-SRC) Beamlines X11a, X11b, X23b National Synchrotron Light Source Brookhaven National Laboratory, Upton, NY 11973 My homepage: http://feff.phys.washington.edu/~ravel EXAFS software: http://feff.phys.washington.edu/~ravel/software/exafs/