Mac CPU task : too long to be true ?

Questions and Answers : Macintosh : Mac CPU task : too long to be true ?
Message board moderation

To post messages, you must log in.

AuthorMessage
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 27 Jun 12
Posts: 11
Credit: 66,233,082
RAC: 25,103
Message 379 - Posted: 16 May 2018, 20:23:04 UTC

Hi Slicker

First thanks a lot to provide a Mac app back in business !

Second I got *one* CPU task (I was hoping to get a GPU one since collatz was almost the only project I was able to use with my old GPU) : it now has more than 3 days of calculation elapsed time, 2 days 20 (hours ?) of effective (reported) calculation, it's only reporting 5,22% of calculation done, remaining estimate 1345 days (!!) and deadline by the 27/05.

Stderr.txt
Collatz Conjecture Sieve 1.40 OS X x86_64
Written by Slicker (Jon Sonntag) of team SETI.USA
Based on the AMD Brook+ kernels by Gipsel of team Planet 3DNow!
Sieve code provided by Sosiris of team BOINC@Taiwan
Collatz Config Settings:
verbose             1 (yes)
lut_size            12 (32768 bytes)
sieve_size          2^26 (4149496 bytes)
cache_sieve         1 (yes)
4237682669897140666395 - 845 steps @ 00:00:00
4237682669897140686271 - 889 steps @ 00:00:00
4237682669897141097919 - 1225 steps @ 00:00:00
4237682669897142179355 - 1362 steps @ 00:00:00
4237682669899342834175 - 1393 steps @ 00:01:24
4237682669902034404635 - 1468 steps @ 00:03:08
4237682669902070853479 - 1530 steps @ 00:03:09
4237682669989356794623 - 1817 steps @ 00:56:36
4237682671919366618783 - 1879 steps @ 16:51:48
Collatz Config Settings:
verbose             1 (yes)
lut_size            12 (32768 bytes)
sieve_size          2^26 (4149496 bytes)
cache_sieve         1 (yes)
4237682676801636139008 6904495472640 60987451118918 1879 2022225952415 4237682669897140666368 4237682722673698799616 117830 197161
Resuming with 4237682669897140666368 at 54:46:01

Out.txt
<soft_link>../../projects/boinc.thesonntags.com_collatz/collatz_sieve_22b5170a-5a00-4deb-9cfd-9e2da65b7aa9_0_r1442190535_0</soft_link>

Checkpoint.txt
18B271F183B04F18D554EA51F5F841F1A27E37A73BE927A9EF06F1671D39A67CBEBDE410ED840136E51DD1E926BAB795EEBEF145797CE6F46C9B62FAACEBC70BDD0E0905828D6AD95C6BB28909BBE231A724081EA7BFAF8C4C3214A5BE4A791E35ED1FB01E365DAE71E99A0CDF26F0B128C9B0A7F41423AE1E0970AC94AE2D4263CA76CBE2EAA7EB9B38BFC00998650EAE3500ECE68DE776363B3CE75C70338335DE67C3C76C1D91

Do you think this is a normal behavior ? should I hope for a better future and let it run or it is already useless ?

Thanks.
ID: 379 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 27 Jun 12
Posts: 11
Credit: 66,233,082
RAC: 25,103
Message 393 - Posted: 17 May 2018, 20:16:43 UTC

Still running, obviously.

Stats are now 4d06 / 3d18 / 11,22% / 1260d...

It advanced 6% in 24 hours so at this rhythm so it would still actually need 2 weeks to complete ?? (but it took 3 days to get to 5%)

What the heck ?
ID: 393 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Slicker
Project administrator

Send message
Joined: 11 Jun 09
Posts: 38
Credit: 766,143,025
RAC: 707,019
Message 396 - Posted: 17 May 2018, 22:29:12 UTC - in response to Message 379.  

There's not much I can do to fix the estimates as BOINC assumes incorrectly that the project does floating point math. Once you finish a couple work units, the estimates should improve. I already set the "estimate is exact" flag on the application but it doesn't seem to have helped much.

I'll double check that the app is compiled with the correct optimization flags and that the symbols are stripped out.
ID: 396 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 27 Jun 12
Posts: 11
Credit: 66,233,082
RAC: 25,103
Message 421 - Posted: 22 May 2018, 16:31:21 UTC

The task has been running for 9 days now. Deadline on the 27/05.

My question was more regarding the reality of such a long execution than the accuracy of the task end estimate.

So for the moment you are saying that I should let it run.

(after such a long time invested I really want to let it finish, I just hope it will actually terminate and will be credited - and will be useful to the project, obviously :) )
ID: 421 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 27 Jun 12
Posts: 11
Credit: 66,233,082
RAC: 25,103
Message 428 - Posted: 23 May 2018, 20:16:29 UTC

Now this bewitched task simply reverted to 2,9% calculated after 10 days of execution (and 9 days processing time) !!

We are now less than 4 days away from the deadline... so I'm going to wait until that date and without further notice from you I will have to cancel it :/


The good news is that today I received a whole bunch of OpenCL tasks on my Mac ! Great ! I'll see how it goes there.
ID: 428 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
[AF>Le_Pommier] Jerome_C2005

Send message
Joined: 27 Jun 12
Posts: 11
Credit: 66,233,082
RAC: 25,103
Message 484 - Posted: 8 Jun 2018, 8:29:55 UTC

I forgot to mention (or "I was too disappointed to talk about it") that the task crashed, I think it was last week and it had already 20 days of calculation and was a week after the deadline but I let it unattended.

Also it's a pity that the project doesn't keep track of past tasks in the user account, my task list is empty.

Needless to say this was the last CPU task I ever try to get.
ID: 484 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Questions and Answers : Macintosh : Mac CPU task : too long to be true ?


©2018 Jon Sonntag; All rights reserved