Wanted a short task for old CPU, got 29 hours

Questions and Answers : Windows : Wanted a short task for old CPU, got 29 hours

To post messages, you must log in.

AuthorMessage
Mastodont

Send message
Joined: 29 Nov 20
Posts: 2
Credit: 1,107
RAC: 0
Message 99811 - Posted: 29 Nov 2020, 2:55:14 UTC
Last modified: 29 Nov 2020, 3:47:45 UTC

My CPU is a fairly old i5 and probably needs a replacement of the thermal paste, so I wanted to run Rosetta for a 2-4 hours a day so I don't abuse it too much. However the first task I got says 1 day 5 hours left. (edit: I see now I have four tasks, ETA of each ranging from 21-28 hours) What did I set wrong? Here are my settings:

COMPUTING PREFERENCES

Suspend when computer is on battery YES
Suspend when computer is in use NO
Suspend GPU computing when computer is in use YES
'In use' means mouse/keyboard input in last 3 minutes
Suspend when no mouse/keyboard input in last --- minutes
Suspend when non-BOINC CPU usage is above --- %
Compute only between ---

Store at least 0.1 days of work
Store up to an additional 0.1 days of work
Switch between tasks every 60 minutes
Request tasks to checkpoint at most every 60 seconds

Use no more than 2 GB
Leave at least 1 GB free
Use no more than 90 % of total

When computer is in use, use at most 40 %
When computer is not in use, use at most 70 %
Leave non-GPU tasks in memory while suspended NO
Page/swap file: use at most 1 %

Network - nothing limited

ROSETTA@HOME PREFERENCES

Resource share 100
Use CPU YES
Is it OK for Rosetta@home and your team (if any) to email you? YES
Should Rosetta@home show your computers on its web site? NO
Default computer location ---
Percentage of CPU time used for graphics not selected
Number of frames per second for graphics not selected
Target CPU run time 2 hours
Graphics background color blue
ID: 99811 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile Grant (SSSF)

Send message
Joined: 28 Mar 20
Posts: 1679
Credit: 17,808,463
RAC: 22,713
Message 99812 - Posted: 29 Nov 2020, 6:22:11 UTC - in response to Message 99811.  

What did I set wrong?
The default Target time is 8 hours, and it appears you have changed that, but the BOINC Manager needs to contact the servers to update that information- which it will have done in order to get the additional Tasks. So by now it should be set for a 2 hour CPU Target Runtime.

However while that is the Target CPU runtime, if a Task needs to run longer in order to complete enough work so it has something it can actually return, it can run for up to an additional 10 hours. However in most cases it should be able to return work in around 2 hours or so.
Also, if your system is busy doing other things while trying to process work, then the Run Time (the time it actually takes to process the Task) can be much longer than the CPU time (the time it actually pends doing the processing); in extreme cases 3 or 4 times longer. But with your system hidden it's impossible to tell if that is at play here.
If using Windows bringing up Task Manager (or better yet using Process Explorer) should let you see what processes are using your CPU. Anything other than rosetta_4.20_windows_x86_64.exe will result in Run times being much longer than the CPU time.
Grant
Darwin NT
ID: 99812 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Brian Nixon

Send message
Joined: 12 Apr 20
Posts: 293
Credit: 8,432,366
RAC: 0
Message 99814 - Posted: 29 Nov 2020, 14:20:54 UTC - in response to Message 99811.  

You didn’t mention how you have configured your CPU usage limits; setting Use at most N % of CPU time less than 100 will certainly increase the wall time required to achieve the target CPU run time.

Rosetta tasks need several hundred megabytes of RAM each; it’s possible that the Memory settings are causing BOINC to stop tasks running (especially if the machine is also being used for other work).

If you’re willing to unhide your computer details (check the option Should Rosetta@home show your computers on its web site? in project preferences), it’ll be easier for us to help.
ID: 99814 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mastodont

Send message
Joined: 29 Nov 20
Posts: 2
Credit: 1,107
RAC: 0
Message 99868 - Posted: 2 Dec 2020, 1:55:22 UTC

Hello again, looks like the estimated time was wrong. All the tasks completed within 4-5 hours of starting. It seems it takes them a long time to get to the first 10% or so, but after that progress starts speeding up. ETA was 8h + until the last 10% though. I'm guessing it's some kind of a worst case estimate, not the average time to finish...
ID: 99868 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Questions and Answers : Windows : Wanted a short task for old CPU, got 29 hours



©2024 University of Washington
https://www.bakerlab.org