Message boards : Number crunching : CPU Overclocking Not Speeding Up Rosetta
Author | Message |
---|---|
Andrew Send message Joined: 2 Dec 16 Posts: 2 Credit: 358,013 RAC: 0 |
Hi, I've been dedicating my computer pretty much 24/7 for Rosetta and overclocked it to speed things up (and keep the house warmer). However, I haven't seen any significant decrease in the time it takes my computer to finish minirosetta work units, about 8 hours give or take depending how much I'm using my computer at the same time. Could someone help me sort this out please? My computer's specs are: i7 5820k overclocked to 4.2Ghz (from 3.3GHz base) running 100% stably 24/7 at about 80C. I have checked it is not throttling and actually running at that speed 16 GB RAM (Rosetta can use up to 80% of this) SSD 950 GTX (used for another BOINC project) Rosetta is allocated up to 100% of cpu and 80% of RAM. Thanks! |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
Each work unit has a flexible number models that can be computed. On faster machines, more models will be completed in a given period of time. What makes a task finish is that the watchdog estimates the next model will cause the task to run past your runtime preference (stated in hours of CPU time). Credit is granted based on the completed models, not the CPU time used. That way credit is based on results, regardless of various CPU and platform capabilities. So, I'd expect that overclocking would cause your machine to earn more credit per hour of CPU... not to complete tasks in less time. Rosetta Moderator: Mod.Sense |
Andrew Send message Joined: 2 Dec 16 Posts: 2 Credit: 358,013 RAC: 0 |
Ah right thank you for the clarification! I'll keep an eye out then for credit per day or something similar. |
rjs5 Send message Joined: 22 Nov 10 Posts: 273 Credit: 23,054,272 RAC: 8,196 |
Ah right thank you for the clarification! I'll keep an eye out then for credit per day or something similar. When I set the PREFERENCES to 24-hours, some of the Rosetta work units would actually complete in less than 24-hours. Then if you speed up your clock OR your make the Rosetta binary faster (as in my performance testing), you can see the AVERAGE TIME for a class of work unit TASKS drop. The run time variations on similar work units can be fairly large (depending on the parameters the researcher selects) so it can be tough to actually see the change. |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
Over time, your RAC will begin increasing. That's the simplest indication that machine machine is doing more work than it used to. But if the machine is not on 24x7, you'd have to exactly match the hours per day the machine is running BOINC as well. Rosetta Moderator: Mod.Sense |
Link Send message Joined: 4 May 07 Posts: 356 Credit: 382,349 RAC: 0 |
Or you can calculate credit per CPU time (not runtime) for each WU. . |
Message boards :
Number crunching :
CPU Overclocking Not Speeding Up Rosetta
©2024 University of Washington
https://www.bakerlab.org