Message boards : Number crunching : WUs taking 25- 50 hours: Is this normal?
Author | Message |
---|---|
DavidVR Send message Joined: 3 Nov 10 Posts: 3 Credit: 578,276 RAC: 0 |
The Rosetta Mini 3.14 WUs are taking several days to complete on a 2.5 GHz C2Q Q8300 CPU. I haven't crunched Rosetta in awhile, and last time I did the WUs were 3- 4 hours. Are such long completion times typical? |
mikey![]() Send message Joined: 5 Jan 06 Posts: 1896 Credit: 9,954,441 RAC: 25,496 ![]() |
The Rosetta Mini 3.14 WUs are taking several days to complete on a 2.5 GHz C2Q Q8300 CPU. I haven't crunched Rosetta in awhile, and last time I did the WUs were 3- 4 hours. Are such long completion times typical? It is probably using the default settings and they are not always optimal for us crunchers. Go into the Boinc Manager and then Advanced, Preferences and click on the 1st tab called 'processor usage'. In there you will find a line that says: "While processor usage is less than [__] percent (0 means no restriction" Put a zero in the box and then click ok at the bottom of the page. This will prevent your crunching from stopping when your cpu is 'busy' doing other stuff. If you use your pc for other stuff experiment with the number until the pc is okay at both. Next on the last tab, disk and memory usage, go to where is stays "tasks checkpoint to disk at most every __ seconds", the default here is 60 seconds and that is quite often. I have mine set to 900 seconds, or 15 minutes, and should be okay as long as your pc doesn't crash more often than that! Next on that same tab but further down under memory usage it says "Use at most __% when computer is in use." I have mine set to 85 and the line below it to 90, all of my computers work just fine with no work stoppages. I think your problem is the other project you are working on is taking away the crunching time making the Rosetta units take a long time. The above changes should help some. |
DavidVR Send message Joined: 3 Nov 10 Posts: 3 Credit: 578,276 RAC: 0 |
The Rosetta Mini 3.14 WUs are taking several days to complete on a 2.5 GHz C2Q Q8300 CPU. I haven't crunched Rosetta in awhile, and last time I did the WUs were 3- 4 hours. Are such long completion times typical? I made the changes you suggested. I also crunch WCG and Collatz so that could be it. Thank you for your help. |
mikey![]() Send message Joined: 5 Jan 06 Posts: 1896 Credit: 9,954,441 RAC: 25,496 ![]() |
The Rosetta Mini 3.14 WUs are taking several days to complete on a 2.5 GHz C2Q Q8300 CPU. I haven't crunched Rosetta in awhile, and last time I did the WUs were 3- 4 hours. Are such long completion times typical? No problem, please report back if it didn't help! |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
Rosetta allows you to set a preference for the work unit runtime you would like to see, and then does it's best to meet that goal. You have to really look at whether you are talking about CPU time per task, or the wall-clock time from when it started until it completed. The above mentioned preference is with regard to CPU time. In other words if you start a task right now, and it runs all afternoon for 10 hours, if your machine was busy with higher priority work, or suspended the tasks due to BOINC reaching your configured memory limitations, or your machine is configured to only run BOINC at 70% of CPU, the tasks may have considerably less then 10 hours of CPU in by the end of the 10 hour period. If you go to the tasks tab and select a task, you can click "properties" and see the actual CPU time. The "elapsed time" shown on the task list is the amount of wall-clock time that the task has been activated to run, but higher priority work (Windows task priorities, not BOINC priorities in this sense) may have prevented it from actually getting CPU time. You can look at your task history and the figures there are CPU seconds used by the task. Rosetta Moderator: Mod.Sense |
Message boards :
Number crunching :
WUs taking 25- 50 hours: Is this normal?
©2025 University of Washington
https://www.bakerlab.org