Hmm... with these new gigabyte size WU's I'm having to scale back my 6gig i7 from 8 wu's to 4 wu's simultaniously.

I've had repeated memory warnings & crashes.

M.

BOINC should be doing that automatically, and avoiding memory warnings and crashes. You may need to limit how much of the machine's page file space it is allowed to use, or expand the size of the swap space on the machine (which is probably what the warnings were about).

---

Rosetta Moderator: Mod.Sense

MOd.Sense said:

expand the size of the swap space on the machine ...

On a windows system this may not make much of a difference - with the 32 bit version of Windows the largest available user address space is 2GB, and the same applies for the 64 bit version of Windows unless the Large_Address_Aware attribute is set.

BTW - Large_Address_Aware is cleared by default.

Let's remember, that's 2GB minus a certain amount of system overhead. With user working set routinely going up to 1.5GB or more, malloc() may be failing due to address space constraints and not a lack of real memory or swap space.

Just about all of my systems are Linux which does not have the 2GB limit on a user address space and despite the fact that I average 1GB or less real memory per core, I am not seeing this problem.

Is anyone seeing this issue on anything other than a Windows box?

BOINC should be doing that automatically, and avoiding memory warnings and crashes. You may need to limit how much of the machine's page file space it is allowed to use, or expand the size of the swap space on the machine (which is probably what the warnings were about).

I'm fiddling with boinc settings.

Well, I'm running boinc on windows 7 64-bit, and prefer to not have the swap file accessed constantly with 8gigs to potentially 16gigs of wu's if all 8 threads are loaded at 1.8 gigs each. I'm thinking of chancing 4 threads.

After getting memory warnings the machine becomes unstable and needs a reboot.

M.