Long wu.

Message boards : Number crunching : Long wu.

To post messages, you must log in.

AuthorMessage
Profile adrianxw
Avatar

Send message
Joined: 18 Sep 05
Posts: 653
Credit: 11,840,739
RAC: 34
Message 68099 - Posted: 15 Oct 2010, 14:12:33 UTC
Last modified: 15 Oct 2010, 14:14:51 UTC

mem_widd_run03_centroid_A_2kdc_SAVE_ALL_OUT_IGNORE_THE_REST_22158_49882 is running a long time. Currently 22:04:57 and 33.038% done. 6 hour run preference set, 31:19:07 estimated remaining...
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
ID: 68099 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 68101 - Posted: 15 Oct 2010, 15:10:12 UTC

If you look at the properties of the task, what does it show for the CPU time used? Do you see the task taking CPU time in the task list? (BOINC Manager shows "elapsed time" now, not CPU time, so you have to look at the task manager on Windows, or top on Linux).
Rosetta Moderator: Mod.Sense
ID: 68101 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile adrianxw
Avatar

Send message
Joined: 18 Sep 05
Posts: 653
Credit: 11,840,739
RAC: 34
Message 68144 - Posted: 20 Oct 2010, 10:49:45 UTC
Last modified: 20 Oct 2010, 10:57:53 UTC

I have not seen this happen with other wu's on this or other machines here, current wu on this machine 2:01:53 and 31% complete with 8:14 to go.

What you say is probably correct, it doesn't alter what I can see. What use is elapsed time? Yet another case of BOINC "improvements" which make it more and more difficult to do anything. It is going downhill at an ever increasing rate.
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
ID: 68144 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 68147 - Posted: 20 Oct 2010, 14:08:16 UTC

Yes, it threw me as well. I believe the idea was to give the user a number that would ALWAYS be moving.

Looks like your problem task finally completed. I shows a preferred runtime of 21600, and that it took just 46 seconds more than that to complete. So that sounds like there was something else running on the machine that was using considerable amounts of CPU. Since BOINC runs at low priority, most anything else gets run first. You can open task manager and sort by CPU time used to see what tasks have been running a lot since you last rebooted the machine. Or sort by CPU% to see tasks that are competing with your Rosetta tasks for CPU right now.
Rosetta Moderator: Mod.Sense
ID: 68147 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : Long wu.



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