log in

Advanced search

Message boards : Number crunching : Remaining time counting backwards

Author Message
minerone
Send message
Joined: 18 Jan 16
Posts: 4
Credit: 24,140
RAC: 0
Message 3672 - Posted: 6 Feb 2016, 12:27:44 UTC
Last modified: 6 Feb 2016, 12:27:44 UTC

I am very new to Boinc and gridcoin.When I started everything worked fine. But after a while I noticed deadlines getting shorter and all my wu would start going backwards. I am letting each wu run at least 1 hour. During this hour the percent done stays at 2%.

example 2d:17:00 thus exceeding the deadline. I see this when the deadline is short but if I catch one that still has 2 days left it will complete.

What should I do?

Christophe Daulie
Send message
Joined: 1 Sep 15
Posts: 1
Credit: 45,593
RAC: 0
Message 3673 - Posted: 6 Feb 2016, 16:55:11 UTC - in response to Message 3672.
Last modified: 6 Feb 2016, 17:00:20 UTC

Yes, I have this problem too.
The percentage stays at 2%, more than 2 hours working and 5days right now to go..
Deadline is this evening.

Update : work for this task done in time.

good luck for everybody

Derion
Send message
Joined: 22 Nov 15
Posts: 29
Credit: 1,084,323
RAC: 0
Message 3678 - Posted: 9 Feb 2016, 8:15:38 UTC
Last modified: 9 Feb 2016, 8:15:38 UTC

The progress bar is not updated continuously, thus inflating the estimated time.

For the Xeon E3 1230 I owned, long tasks take around two and a half hour to finish.

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 247
Credit: 1,456,117
RAC: 0
Message 3679 - Posted: 9 Feb 2016, 17:35:44 UTC
Last modified: 9 Feb 2016, 17:35:44 UTC

The python Jobs currently stay at 2% until they are completed, We will work to find a way to fix this issue.

I will take a look to make sure deadline issues are not occurring

Thanks for supporting us and happy crunching,

Brandon

minerone
Send message
Joined: 18 Jan 16
Posts: 4
Credit: 24,140
RAC: 0
Message 3685 - Posted: 9 Feb 2016, 20:55:33 UTC - in response to Message 3679.
Last modified: 9 Feb 2016, 20:55:33 UTC

Ok instead of aborting I went ahead and just let it run! At around 2.5 elasped time they did stop and were uploaded.

I set a stop watch to run in conjuction and got a real big difference. Each WU ran more than 4 hours of real time.

BobCat13
Send message
Joined: 29 Jan 08
Posts: 18
Credit: 202,217
RAC: 0
Message 3686 - Posted: 9 Feb 2016, 21:15:58 UTC - in response to Message 3685.
Last modified: 9 Feb 2016, 21:15:58 UTC

Ok instead of aborting I went ahead and just let it run! At around 2.5 elasped time they did stop and were uploaded.

I set a stop watch to run in conjuction and got a real big difference. Each WU ran more than 4 hours of real time.

Are your preferences set to run the CPU at 60%?

My CPU is set to 100% and tasks end at approximately 2:29 elapsed time or 149 minutes. 149/0.6=248.333~ or 4 hours, 8 minutes, 20 seconds of real time.

minerone
Send message
Joined: 18 Jan 16
Posts: 4
Credit: 24,140
RAC: 0
Message 3687 - Posted: 9 Feb 2016, 21:42:50 UTC - in response to Message 3686.
Last modified: 9 Feb 2016, 21:42:50 UTC

That answers my question thanks! Yea I am running my cpu's at 60% to keep the heat down.

minerone
Send message
Joined: 18 Jan 16
Posts: 4
Credit: 24,140
RAC: 0
Message 3689 - Posted: 11 Feb 2016, 21:25:57 UTC - in response to Message 3687.
Last modified: 11 Feb 2016, 21:25:57 UTC

This is even better lol I wait then try again.... I get task due on the 16th but when they start I get Computation error!

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 247
Credit: 1,456,117
RAC: 0
Message 3691 - Posted: 13 Feb 2016, 18:45:54 UTC
Last modified: 13 Feb 2016, 18:46:11 UTC

Thanks for letting us know minerone.

We will take a look at this as soon as we can.

Thanks for supporting us and happy crunching,

Brandon

Message boards : Number crunching : Remaining time counting backwards


Main page · Your account · Message boards


Copyright © 2018 MindModeling.org