Rosetta@Home - I GIVE!

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
25,560
14,513
136
Is it the slow core or because Rosetta is using all your RAM?
I don't know, but all the affected boxes had ram available, but only ONE thread for the fast boxes and 2 for the 7B12. So, Rosetta on hold for all those boxes until I find a good number.
 

Skillz

Senior member
Feb 14, 2014
926
951
136
I thought most of your bigger rigs couldn't run a lot of rosetta tasks because they ran out of RAM? Like the 256 thread EPYCs would only be able to run around 120 rosetta tasks because they didn't have enough RAM to run all threads?
 

Markfw

Moderator Emeritus, Elite Member
May 16, 2002
25,560
14,513
136
I thought most of your bigger rigs couldn't run a lot of rosetta tasks because they ran out of RAM? Like the 256 thread EPYCs would only be able to run around 120 rosetta tasks because they didn't have enough RAM to run all threads?
But it was happening on a 3950x with 64 gig ram running 31 tasks. Yes, the other 2 7742,s are out of memory, but working fine. Its cores, not ram, or could be both.

I should fire up the dual 7601 system and Run Rosetta only on it. (if I don't blow circuit breakers) Its 256 gig for 128 threads.
 

Skillz

Senior member
Feb 14, 2014
926
951
136
But it was happening on a 3950x with 64 gig ram running 31 tasks. Yes, the other 2 7742,s are out of memory, but working fine. Its cores, not ram, or could be both.

I should fire up the dual 7601 system and Run Rosetta only on it. (if I don't blow circuit breakers) Its 256 gig for 128 threads.

Doesn't Rosetta@home use 2GB per task? So 31 * 2 = 62GB of RAM out of 64GB available. 2GB for Windows/Linux and F@H isn't enough.
 

StefanR5R

Elite Member
Dec 10, 2016
5,512
7,818
136
To avoid swapping to disk, try this:
  • Shut down the boinc client.
    (Alternatively, switch "Leave non-GPU tasks in memory while suspended" off, then suspend all active projects.)
  • Watch how much RAM is occupied by Folding@home, the operating system, and what else is typically running on this computer.
  • Turn boinc client back on, and set both "Memory | When computer is/ is not in use, use at most __%" to a percentage which is what remains if deduct the memory footprint for F@h and all the rest, and a safety margin of, say, 4 GB.