workunit progress was 48%, now down to 8% - what is happening?

Questions and Answers : Unix/Linux : workunit progress was 48%, now down to 8% - what is happening?
Message board moderation

To post messages, you must log in.

AuthorMessage
john

Send message
Joined: 12 Sep 15
Posts: 1
Credit: 59,503,023
RAC: 0
Message 2955 - Posted: 28 Oct 2020, 17:04:51 UTC

I have a workunit that has been running over 10 days now, last night it was at 48%, this morning it is at 8%, and the estimated time to completion is now over 10 days. Is this common?
The work unit properties:

Application
Collatz Sieve 1.40
Name
collatz_sieve_4ca56b99-5ebe-4611-983a-fd7c0a4ab36c
State
Running
Received
Thu 15 Oct 2020 11:36:01 PM CDT
Report deadline
Thu 29 Oct 2020 11:44:05 PM CDT
Estimated computation size
417,339,904 GFLOPs
CPU time
11d 02:19:17
CPU time since checkpoint
00:00:04
Elapsed time
11d 03:12:42
Estimated time remaining
10d 15:40:18
Fraction done
8.711%
Virtual memory size
12.68 MB
Working set size
10.51 MB
Directory
slots/0
Process ID
20437
Executable
collatz_sieve_1.40_x86_64-pc-linux-gnu

Thanks,
John Reeves
ID: 2955 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile mikey
Avatar

Send message
Joined: 11 Aug 09
Posts: 910
Credit: 24,523,632,110
RAC: 0
Message 2956 - Posted: 28 Oct 2020, 19:45:25 UTC - in response to Message 2955.  

I have a workunit that has been running over 10 days now, last night it was at 48%, this morning it is at 8%, and the estimated time to completion is now over 10 days. Is this common?
The work unit properties:

Application
Collatz Sieve 1.40
Name
collatz_sieve_4ca56b99-5ebe-4611-983a-fd7c0a4ab36c
State
Running
Received
Thu 15 Oct 2020 11:36:01 PM CDT
Report deadline
Thu 29 Oct 2020 11:44:05 PM CDT
Estimated computation size
417,339,904 GFLOPs
CPU time
11d 02:19:17
CPU time since checkpoint
00:00:04
Elapsed time
11d 03:12:42
Estimated time remaining
10d 15:40:18
Fraction done
8.711%
Virtual memory size
12.68 MB
Working set size
10.51 MB
Directory
slots/0
Process ID
20437
Executable
collatz_sieve_1.40_x86_64-pc-linux-gnu

Thanks,
John Reeves


You are not giving it enough cpu time to run, your settings probably stop crunching if the pc is 'in use' and you don't stop using it. Your other pc the Windows 10 one would probably run gpu tasks if you tried but they would take awhile, not NEARLY as long as this unit but half an hour maybe.

To be honest not many people run cpu tasks here as they take a long time, not as long as yours is, and don't give out the credits for the time like the gpu tasks do.
Since it's a linux pc you can run the Giaia Project http://150.254.66.104/gaiaathome/ or the Wanless Project http://bearnol.is-a-geek.com/wanless2/ that Windows pc's can not run. Both ARE Boinc Projects but they are small and Giaia is brand new and working on being stable, while Wanless has been around for a few years. If you are interested in Covid-19 research World Community Grid https://www.worldcommunitygrid.org/ still has those under the Open Pandemic sub project. The Project TN-Grid http://gene.disi.unitn.it/test/ also has Covid-19 tasks sometimes but like Giaia rarely has hundreds of tasks to download.
ID: 2956 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Questions and Answers : Unix/Linux : workunit progress was 48%, now down to 8% - what is happening?


©2021 Jon Sonntag; All rights reserved