I have 512mb of Memory on each machine all AMD processors running windows XP,Boinc Ver 5.8.11, to get work to my machines, I have three, I set my preferences to 100% on all of the following; % of page swaping, Memory when in use & Memory when machine is idle.

---

I had the same problem earlier, but then I upgraded BOINC which in turn upgraded RAH and the problem was solved, but then the WU I was on crashed with a unrecoverable error. I had a ABRELAX Frags WU running at the time.

Anyway, I have moved on to Hinge WU's now.

---

I finally got one of the HINGE W.U. after changeing the memory

% up to 95% for both and 80% for swapfile. See other thread for others.

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=2943

P.S. I just hope it runs.

---

I have two machine out of work that are running "older" BOINC Core Clients One has 512 Meg of RAM and the other has 256 Meg of RAM... In both cases the Server is not honoring older BOINC Core Clients

I went through adjusting "preferences" and the report was still that same...

That is Server Side Issue...

Hopefully someone is scrambling to figure out what happened... This is not appearing across the 5 Projects that I am working...

---

...None of my machines are graphics loaded.. too much much work for too little return...

Exactly my strategy.

btw, for Linux users, if you want a more detailed breakdown of memory usage for the machine as a whole, including swapfile, disk cache, etc, try

cat /proc/meminfo

which provides a listing with headings of all kinds of memeory related stuff. The Swapfile free is a useful indicator - if it is almost as big as the total swapfile size then your box is not suffering too much.

For the one process, you could try (where [pid] is the proces id number from top) cat /proc/[pid]/status

R~~

The BOINC server code is not as specific as to distinguish between a Linux system with reduced RAM operating system, and no graphics, from a Windows system with 50MB of extra drivers loaded and full graphics enabled. So the memory requirement pertains to the created task, not to the operating system that happens to download it.

The Project Team has loaded the queue with more tasks for systems with only the minimum memory requirement.

---

Rosetta Moderator: Mod.Sense

The BOINC server code is not as specific as to distinguish between a Linux system with reduced RAM operating system, and no graphics, from a Windows system with 50MB of extra drivers loaded and full graphics enabled. So the memory requirement pertains to the created task, not to the operating system that happens to download it.

Exactly my point.

But when the task arrives on a box that is asking to display graphics (explicitly or the screensaver) it loads lots of gfx code from the shared libraries (.so on Linux, .dll on Windows). When it arrives on a machine that does not want gfx, it does not load that code. If it tried to on my machine it would fall over (as the Leiden WU do).

So the same task runs in two very different sizes depending where it lands. This is nothing to do with the code used by the OS, it is code selectively loaded by the Rosetta app as required.

Which means the mem requirement is either wrong for a user with graphics, or is wrong for a user without.

This problem must exist on every project that reponds properly to the presence/absence of graphics. It is a BOINC issue not a ROsetta issue, but at present it is affecting all of us who don't want graphics. In effect we are being told to provide enough RAM for the graphics we don't want...

R~~

---