Message boards :
Number crunching :
BOINC est time limit is 86600:00:00
Message board moderation
Author | Message |
---|---|
Send message Joined: 8 Apr 10 Posts: 25 Credit: 268,525 RAC: 0 |
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 |
Send message Joined: 7 Jun 08 Posts: 464 Credit: 56,639,936 RAC: 0 |
LOL... Yes, inaccurate (term used loosely) runtime estimates is a known issue with 1.04 at this point. |
Send message Joined: 11 Dec 08 Posts: 1 Credit: 17,143,443 RAC: 0 |
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. |
Send message Joined: 8 Apr 10 Posts: 25 Credit: 268,525 RAC: 0 |
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 |
Send message Joined: 7 Jun 08 Posts: 464 Credit: 56,639,936 RAC: 0 |
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. |
©2024 Astroinformatics Group