Welcome to MilkyWay@home

BOINC est time limit is 86600:00:00

Message boards : Number crunching : BOINC est time limit is 86600:00:00
Message board moderation

To post messages, you must log in.

AuthorMessage
EdwardPF

Send message
Joined: 8 Apr 10
Posts: 25
Credit: 268,525
RAC: 0
Message 56898 - Posted: 15 Jan 2013, 20:35:10 UTC
Last modified: 15 Jan 2013, 20:36:15 UTC

But I 'm guessing the nbody orphan_real will finish sooner ... :-)

Est task size: 2301211000 GFLOPs

2.9% in 3:36:00 ... I duess I'll give it more CPU's

Ed F

[edit] thats 87600:00:00
ID: 56898 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Alinator

Send message
Joined: 7 Jun 08
Posts: 464
Credit: 56,639,936
RAC: 0
Message 56904 - Posted: 16 Jan 2013, 1:04:22 UTC - in response to Message 56898.  

LOL...

Yes, inaccurate (term used loosely) runtime estimates is a known issue with 1.04 at this point.
ID: 56904 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Eric Nietering

Send message
Joined: 11 Dec 08
Posts: 1
Credit: 17,143,443
RAC: 0
Message 56905 - Posted: 16 Jan 2013, 4:05:25 UTC

I have a similar issue:

WU: de_nbody_100K_104_1_1356215205_103909

Est comp size: 5648370000 GFLOPS

Est time left: 56936:47:28
2.471% complete in 27 hours

Every few minutes it does add another thousandth of a percent, so it is running.
ID: 56905 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
EdwardPF

Send message
Joined: 8 Apr 10
Posts: 25
Credit: 268,525
RAC: 0
Message 56906 - Posted: 16 Jan 2013, 5:11:48 UTC - in response to Message 56905.  

Mine errored out with disk limit exceeded 87.80 Mb exceeds 50.00 Mb.

The est time NEVER went down ... it was stuck at 87600:00:00

I don't see a 50.00 MB limit on disk space so I assume it's imposed by the WU.

Ed F
ID: 56906 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Alinator

Send message
Joined: 7 Jun 08
Posts: 464
Credit: 56,639,936
RAC: 0
Message 56913 - Posted: 16 Jan 2013, 11:16:17 UTC - in response to Message 56906.  
Last modified: 16 Jan 2013, 11:26:33 UTC

The interesting part here is your faulted out but reported zero for elapsed and CPU time, whereas the wingman at least had logged time on it.

In any event, the error was the same and seems to be confined to the 'orphan_real' tasks and its subtypes.

<edit> The 2 orphan_real tasks I mentioned are getting close to completion now. The 112_ subtype had a CP size 27877284 bytes and the CHISQ one is 9685220 bytes. Both have remained constant since I started watching them.

So I guess this would indicate the limit problem is more a function of what is coming out in the wash as the task is processing, than a specific bug with the app per se. IOW's, 'bad' or misconfigured WU's.
ID: 56913 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : BOINC est time limit is 86600:00:00

©2024 Astroinformatics Group