Brahms, I have not been invloved in any discussions about proof, but we do have a major problem with memory. Last night I ran a proof session which died on me because it used up all the available memeory. Now there was nothing special about this session other than I was testing out my code. Now there could be somehting wrong with my code, but this does not explain why a proof session uses up more and more memory when I do NOTHING!!! Now if I want to load in a number of libraries, I'm using up more memory at the start. Yesterday I ran over all the auau 200GeV data filling a number of histograms. I created 8622 histograms (a good number of them were not filled with any events) in a proof session. The session ran fine. Last night, I ran another session to test some code and I tried to process all of the auau 200GeV data. I created 11 histograms, loaded in a library, and the proof session hung with a memory leak. Here is the responce I got from RCF OK - I'll reboot some of the nodes that are still down but Brahms needs to come to grips with how to run proofserv. You can't expect to run multiple proofserv processes >1.7GB each without driving swap down to ZERO, even with 2G of memory, possibly crashing it. If this occurs on a weekend, you will have to wait until Monday. Open to suggestions if there is anything we can do at this end. --Richard Hogue Now does anyone have a good idea on how one can approach and fix this problem? Erik _______________________________________________ Brahms-dev-l mailing list Brahms-dev-l@lists.bnl.gov http://lists.bnl.gov/mailman/listinfo/brahms-dev-lReceived on Fri Mar 24 11:46:22 2006
This archive was generated by hypermail 2.1.8 : Fri Mar 24 2006 - 11:46:36 EST