• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Good DC apps that take lots of RAM?

VirtualLarry

No Lifer
Just curious. I'm upgrading my twin desktop rigs, that now have Q9300 @ 3.0 in them and GTX 460 1GB cards, to 8GB of RAM each. Running Win7 64-bit HP.

Doing F@H on one rig, but thought that perhaps I could try something different on the other rig, preferably something that actually uses 4GB+ of RAM. Anything like that out there? Or do they also require a hyperthreaded quad-core or more?
 
Cosmology@home requires a lot of RAM. I am running a quadcore with 3 GByte RAM (Win XP pro) and when a WU is getting close to the end the message "Waiting for memory" appears for one of the WUs (usually not the one which is closest to being finished....).
 
RNA World (beta) also requires a lot of RAM. It all depends of the WUs you get but with a quad core, 4 gigs of RAM, I've see the "waiting for memory" message too. One annoying issue with RNA World, no checkpointing either. Some of the WUs (1% or so?) can run for days on end. If you reboot or stop/start boinc, you've lost several days of work w/ the long WUs. They now give 2X points on the long ones though.
 
Another question: I installed 8GB (4x2GB) HP ECC unbuffered RAM, into each of my P35-DS3R boards. I know I can't actually use the ECC. but other than that, it's compatible.

But the SPD timings on these sticks are 5-5-5-15 at 333Mhz, and 6-6-6-18 at 400Mhz.

I tested them with Memtest86+ 4.10 at 5-5-5-15 at 400Mhz and there were no errors.

Do you think it's safe to use the tighter, arguably more standard timings, for DC work? I don't want bit-flips (if only my chipset supported ECC too!), but if it tested ok?
 
Last edited:
Testing with memtest won't be enough, I would test with OCCT for 24hrs & then with F@H SMP for a week, & if it passes those (ie no EUEs with F@H) then I would consider it stable.
 
Testing with memtest won't be enough, I would test with OCCT for 24hrs & then with F@H SMP for a week, & if it passes those (ie no EUEs with F@H) then I would consider it stable.

Ok. Running F@H SMP on all four cores, for several days now, will continue and monitor results.
 
Back
Top