log in

Advanced search

Message boards : Number crunching : The Deadline is too short !!!

1 · 2 · 3 · Next
Author Message
Profile [SG]bieboderbeste
Send message
Joined: 6 May 09
Posts: 1
Credit: 271,173
RAC: 0
Message 3564 - Posted: 31 Oct 2015, 15:35:38 UTC

I become many Workunits this Day. But they came in 31.10.2015 16:00 and the Deadline is 31.10.2015 18:00
The runtime for the most Units is around 2-3 Hours for my PC´s
What´s going on ???

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 263
Credit: 1,456,117
RAC: 0
Message 3566 - Posted: 2 Nov 2015, 19:23:48 UTC

Hello [SG]bieboderbeste,

Thanks for letting us know. The issue has been resolved and the deadlines are back to normal now.

I will continue to watch your work units for abnormal deadlines

Thanks for your support, and happy crunching,

Brandon

Matthias Lehmkuhl
Send message
Joined: 29 Mar 08
Posts: 27
Credit: 398,263
RAC: 78
Message 3567 - Posted: 4 Nov 2015, 12:48:36 UTC

for me the deadline is very short
Native Python v2.7 Application (Cross Platform) v1.10 (sse2)
http://mindmodeling.org/result.php?resultid=9100239
send time: 4 Nov 2015, 11:33:42 UTC
end time : 4 Nov 2015, 17:33:42 UTC

OK, its 6 hours now, but this is very short for computers that will not run 24/7

runtime is round 9000 seconds (2:30 hours) on my computer
____________
Matthias

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 263
Credit: 1,456,117
RAC: 0
Message 3568 - Posted: 4 Nov 2015, 22:11:14 UTC

Hello Matthias Lehmkuhl,

I extended the deadline for this job so you shouldn't run into anymore issues with deadlines for the time being.

If you need anything else please let me know.

Happy Crunching,

Brandon

nasher
Send message
Joined: 11 Jun 08
Posts: 1
Credit: 18,699
RAC: 0
Message 3569 - Posted: 6 Nov 2015, 17:30:30 UTC

with the headlines like they are and the time to complete are off i am going to have to pause working these for a bit. it just overrides my settings

Dayle
Send message
Joined: 10 Oct 13
Posts: 9
Credit: 612,440
RAC: 0
Message 3621 - Posted: 18 Jan 2016, 14:17:34 UTC
Last modified: 18 Jan 2016, 14:17:34 UTC

Deadline is STILL too short.
I just had three work units marked as Invalid after being returned within eight hours.

http://mindmodeling.org/workunit.php?wuid=20914491
http://mindmodeling.org/workunit.php?wuid=20912796
http://mindmodeling.org/workunit.php?wuid=20912630

PRL
Send message
Joined: 2 Aug 09
Posts: 4
Credit: 82,710
RAC: 10
Message 3622 - Posted: 18 Jan 2016, 16:44:20 UTC
Last modified: 18 Jan 2016, 16:44:20 UTC

I am typically only getting 6 hours. Any hiccups and I get 'Timed out - no response' or 'Not started by deadline - canceled'. Until this is resolved I have set BOINC not to get new tasks for this project. I am wasting processing time.

Dayle
Send message
Joined: 10 Oct 13
Posts: 9
Credit: 612,440
RAC: 0
Message 3627 - Posted: 19 Jan 2016, 5:50:22 UTC
Last modified: 19 Jan 2016, 5:50:22 UTC

Check this work unit out. Three different hosts timed out on the same work unit. And I'll bet we all finished it too. Could have saved everyone a LOT of wasted crunching power....

https://mindmodeling.org/workunit.php?wuid=20944893

MindCrime
Send message
Joined: 26 Mar 14
Posts: 3
Credit: 246,065
RAC: 0
Message 3628 - Posted: 19 Jan 2016, 22:00:01 UTC - in response to Message 3627.
Last modified: 19 Jan 2016, 22:00:01 UTC

After noticing quite a few "invalids" I see that they were not finished in time. As I write this it is 1/19/2016 (jan 19th) 2pm, The WUs I am recieving expire at 1/19/2016 7:51pm, I always thought the deadline times were UTC, which I now see they're UTC on the website, and localized on BOINC client.

Anyways yes 6 hours is ridiculous, please adjust.

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 263
Credit: 1,456,117
RAC: 0
Message 3639 - Posted: 22 Jan 2016, 14:25:26 UTC
Last modified: 22 Jan 2016, 14:25:26 UTC

Hey guys,

Here is how the work unit deadlines work currently.



By default our work units will now have a 5-day turn around time.

However, the work units at either the very beginning, or at the end of a batch of work, will have a < 1-day turn around time.

< 1-day turn around at beginning of the batch of work:
This allows us to get the modeler important information regarding their model faster, just in case a problem arises, and they need to stop the job early.

< 1-day turn around at end of batch of work:
This allows the job that is almost done to finish quickly, and get initial results on new work earlier.

The bulk of the work units in the middle will stay at the 5-day turn around time, and hopefully this fixes the issues you guys are having.



This current job is at the beginning so that's why the work unit deadline times are short but it will not stay this way throughout the entire job.

Let me see what I can do to help fix this and I will get back to you guys.

Thanks for supporting us and happy crunching,

Brandon

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 263
Credit: 1,456,117
RAC: 0
Message 3642 - Posted: 22 Jan 2016, 15:59:42 UTC
Last modified: 22 Jan 2016, 16:05:45 UTC

The timeout issue has been resolved so all the work units available currently should not be giving you guys issues as far as timing out is concerned.

Thanks for supporting us and happy crunching,

Brandon

marmot
Send message
Joined: 6 Dec 15
Posts: 12
Credit: 2,071,787
RAC: 0
Message 3676 - Posted: 7 Feb 2016, 6:22:22 UTC
Last modified: 7 Feb 2016, 6:35:14 UTC

This is happening to me today.

I have several WU that were asked for and the machine needed 3 hours to do and got 2 done and then the server aborted the rest (timed out) while they were still working on them. Deadline was about 3 to 5 hours on about 20 WU's.

The machine was still working on these (it had been working on prior one that was past the short deadline) but I got this in the logs:

12826265 21911390 6 Feb 2016, 23:46:44 UTC 7 Feb 2016, 6:19:28 UTC Timed out - no response 0.00 0.00 --- Native Python v2.7 Application (Windows Only) v1.10 (sse2)
12826370 21903657 6 Feb 2016, 23:45:53 UTC 7 Feb 2016, 6:18:37 UTC Timed out - no response 0.00 0.00 --- Native Python v2.7 Application (Windows Only) v1.10 (sse2)

Looks like the last 50+ WU's all have 5 to 6 hour deadlines.

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

Thanks for letting us know marmot,

We will take a look at this and let you know if we find anything.

Thanks for supporting us and happy crunching,

Brandon

Profile Brandon
Project administrator
Project developer
Project tester
Avatar
Send message
Joined: 5 Jan 15
Posts: 263
Credit: 1,456,117
RAC: 0
Message 3684 - Posted: 9 Feb 2016, 18:13:10 UTC
Last modified: 9 Feb 2016, 18:14:03 UTC

Hey Guys,

Just wanted to give you an update. Our system stops work units automatically if they use more than 2.5 hours of compute time.

This past job we believe was distributing more than 2.5 hours of work to be computed in some of the work units and this is what caused the error.

We are working with the modeler to resolve this issue and the next job released should not have this issue.

Thanks for letting us know and for all your support.

Happy Crunching,

Brandon

Jacob Klein
Send message
Joined: 9 Oct 09
Posts: 37
Credit: 333,573
RAC: 0
Message 3692 - Posted: 21 Feb 2016, 22:25:24 UTC - in response to Message 3639.
Last modified: 21 Feb 2016, 22:34:59 UTC

Brandon,

I don't think you understand another one of the issues that has been reported previously*, regarding short deadlines. Please read this.

The tasks that have quick 5-6 hour deadlines, are causing all of my GPUs to go idle, because I am attached to 50 other projects, and your super-fast-deadlines cause BOINC to think that your project's tasks need to be ran immediately (they go into "earliest-deadline-first" panic/priority mode, and get scheduled ahead of my GPU tasks).

I don't want my GPUs to go idle like this, but I do want to help your project.

What you should do is have a 5-day deadline for most tasks. And then any other tasks that need faster deadlines should be in their OWN APPLICATION. That way, users who want to skip the fast-deadline tasks, can edit their MindModeling project preferences to not get tasks from that app.

Without such a feature, then I must set your project for No New Tasks, and stop helping, for my hosts that have GPUs. You give me no choice.

I highly recommend you separate the fast-return tasks into their own application. I've mentioned this several months ago, and you seem to gloss over my recommendation, sadly.

Kind regards,
Jacob Klein

*
https://mindmodeling.org/forum_thread.php?id=1024
https://mindmodeling.org/forum_thread.php?id=667

Derion
Send message
Joined: 22 Nov 15
Posts: 30
Credit: 1,208,106
RAC: 148
Message 3694 - Posted: 23 Feb 2016, 23:39:21 UTC - in response to Message 3692.
Last modified: 23 Feb 2016, 23:39:21 UTC

I noticed some of the wu yesterday were marked with 5-day deadline, but most of them are still six-hours. I thought they have made the changes for good :/

Jacob Klein
Send message
Joined: 9 Oct 09
Posts: 37
Credit: 333,573
RAC: 0
Message 3695 - Posted: 24 Feb 2016, 0:23:17 UTC - in response to Message 3694.
Last modified: 24 Feb 2016, 0:24:17 UTC

I noticed some of the wu yesterday were marked with 5-day deadline, but most of them are still six-hours. I thought they have made the changes for good :/


Nope.

Per this message:
https://mindmodeling.org/forum_thread.php?id=1024&postid=3638
... they still have tasks with deadlines tighter than 5 days, which then preempt tasks from other projects and tasks that run on GPUs.

Since I prefer to keep my GPUs busy, and since they haven't separated the tight-deadline-tasks into their own application that I can disable, then .. I have no choice but to set this project for No New Work.

marcuac
Send message
Joined: 18 Jan 16
Posts: 1
Credit: 39,475
RAC: 0
Message 3704 - Posted: 1 Mar 2016, 1:51:30 UTC
Last modified: 1 Mar 2016, 1:51:30 UTC

I've been running BOINC for many years and just recently came across and added MindModeling to my list of projects. But I soon noticed the super short deadline issue which causes BOINC to always run these tasks in high priority mode at the expense of all the other projects.
So, since it doesn't play well with others I was forced to set it to not accept new tasks. It will stay that way until the deadlines are set similar to other projects out there so each can run its fair share. Most other projects have 1-2 weeks deadlines, this one up to 2 days from what I observed so far.

Please fix soon, it's an interesting project and I would like to resume participating.

Regards.

Derion
Send message
Joined: 22 Nov 15
Posts: 30
Credit: 1,208,106
RAC: 148
Message 3741 - Posted: 11 May 2016, 23:13:19 UTC
Last modified: 11 May 2016, 23:13:19 UTC

Short deadline happening again after the last batch with reasonable ones.

Crackenback
Send message
Joined: 28 Aug 09
Posts: 3
Credit: 265,703
RAC: 0
Message 3744 - Posted: 20 May 2016, 0:40:08 UTC
Last modified: 20 May 2016, 0:40:08 UTC

I agree with marcuac. I've had to halt getting more work from MindModeling as it is causing problems with other projects due to the short deadlines. Almost all of the new WU's go straight to the top of the work queue and prevent any other projects from getting a turn.

Perhaps add a note for applications with short deadlines in project preferences. This is so those who only crunch for MindModeling can focus there while those who crunch multiple projects can avoid apps with short deadline WUs.

I do like the science behind this and hope this issue is resolved for good so I can accept WUs and contribute again.

Cheers.

1 · 2 · 3 · Next

Message boards : Number crunching : The Deadline is too short !!!


Main page · Your account · Message boards


Copyright © 2018 MindModeling.org