The only problem I have with rosetta@home is the memory usage. I have only 256MB of memory and rosetta takes more than 100MB.
Is there any objectives to reduce the memory usage ?

Thanks (and sorry for my English level :))

They have already made an effort to reduce memory usage. So, more reduction in memory usage is not likely. If Rosetta is interfering with your use of your computer, you might set your general preferences to leave applications in memory while suspended (don't worry, it will page it out to disk), and to NOT run while the computer is in use. Or, you could set it to only run during hours of the day when you aren't using your computer.

Another approach, if your computer has more then one CPU, would be to set the general preference to use at most one CPU.

---

Yes, I remind they made an effort to reduce de memory usage (rosetta took less than 60mb). But the last applications never take less than 60mb.

Yes, I remind they made an effort to reduce de memory usage (rosetta took less than 60mb). But the last applications never take less than 60mb.

I have been running Ralph for a couple of months now, and all of a sudden today the server refuses to download WU's to one of my machines because it only has 256MB of memory. This machine has crunched 275 WU's without a hiccup, so why all of a sudden is it not good enough?

Edit: I just watched the memory usage for the last 30 min. The lowest it used was 31MB and then would climb slowly to around 70-75MB then would drop back to 31. So as you can see it didn't even have to use the VM!

---

Silver Streak

The project team is making every effort to assure that the crunching does not interfere with your usage of your computer. To that end, they have two "sizes" of WUs. Some that are "normal" which run on the minimum required memory of 256MB, and others which are "large" which they know ahead of time will require more memory to complete then normal work units.

Part of the purpose of Ralph is to test the WUs. Since there is a human element to building them, there are potential problems. By testing a set of WUs on Ralph first, it helps assure things go smoothly on Rosetta.

The WUs on Ralph tend to come out in batches. And they must now be on to a batch of WUs which are "large". These WUs are only sent to machines with 512MB or more of memory... regardless of any other factors about how it is a dedicated cruncher, or never has to use the swap file.

So, it's not that your computer "isn't good enough". Just that it has <512MB of memory and will not be sent "large" WUs. This is a good test for Ralph, to assure that it enforces this WU requirement correctly. I'm sure they will be back to testing normal WUs soon, so don't be discouraged.

...and I think the 512MB figure is "per CPU", but I'm not clear on the details on how that works.

...wow! a RAC of 3568 on RALPH? You DO KNOW that Ralph is a test project, and the bulk of your crunch time would be preferred on Rosetta, right? I set up my resource share so that Ralph gets 10% of what I give to Rosetta. Since there are not WUs available all the time on Ralph, that seems to be a pretty good balance between trying constantly to get work when none is available for days, and not having any debt to Ralph when work does become available. Just a suggestion.

---

Rosetta would be more attractive with a with a low use of the memory.. :(
It's frustrating not to crunch for a project that we like because of the system requirement.