You now have a class of WUs that are flagged for 1GB and higher systems. And you\'ve asked us to monitor memory usage... presumably these 1GB units are going to need more memory than the norm... but how do we know which is which?

I\'ve got one here called T0287_HOMOLOG_ABRELAX_hom019_539_85 that looks like I could wrap it around my HOUSE! An ya, it\'s using more memory, as one would expect.

Could you give us a feel for what you want us to be observing and which WUs are known to need more memory than the new and improved lower norm of about 100MB??

You now have a class of WUs that are flagged for 1GB and higher systems. And you\'ve asked us to monitor memory usage... presumably these 1GB units are going to need more memory than the norm... but how do we know which is which?

I\'ve got one here called T0287_HOMOLOG_ABRELAX_hom019_539_85 that looks like I could wrap it around my HOUSE! An ya, it\'s using more memory, as one would expect.

Could you give us a feel for what you want us to be observing and which WUs are known to need more memory than the new and improved lower norm of about 100MB??

[edit] ...and is it 1GB per CPU? Or per system?

Actually they seem to be abandoning the idea. They have decided to run the very largest memory hogs in another area of the project. It seems the research was different than the main thrust of Rosetta to begin with. But more importantly, those work units had some very bad memory leak problems they are tracking down, and they can\'t put them out on the production system. So the focus now is to kill the last major bug, reduce the memory footprint of all the work units, incorporate the new techniques they are trying, to produce more efficient code, and optimize what they can in the applications.

To that end they are all very busy right now.Moderator9
RALPH@home FAQs
RALPH@home Guidelines
Moderator Contact