Just browsing my WU's after all my SETI's have cleared (a couple of pages) . I just came across a work unit doomed to run out of time. Apparently it was recieved on 6th of Feb. based on it's properties, it has still not run yet (26th Feb) but... get this, it's report deadline is on 3/3/10, only a week away, but will apparently take 941:54:01 to complete!!!! That's almost 40 days!! There's no way it will complete. First my home pc is on a max of 5-6hrs/day and BOINC suspends/run tasks! (I have 4 other projects) Based on the day I got it - it would have STILL run out of time from the word go!!
It's an AstroPulse v505 5.05 WU.
'ap_01dc06ac_B0_P1_00247_20100206_19920.wu_1'
Should I abort it before even trying..?

I have:
Processor: 2 GenuineIntel Intel(R) Pentium(R) D CPU 2.80GHz [x86 Family 15 Model 4 Stepping 7]
with
NVIDIA GPU 0: GeForce 8800 GT (driver version 19621, CUDA version 3000, compute capability 1.1, 512MB, 381 GFLOPS peak)

---

Just browsing my WU's after all my SETI's have cleared (a couple of pages) . I just came across a work unit doomed to run out of time. Apparently it was recieved on 6th of Feb. based on it's properties, it has still not run yet (26th Feb) but... get this, it's report deadline is on 3/3/10, only a week away, but will apparently take 941:54:01 to complete!!!! That's almost 40 days!! There's no way it will complete. First my home pc is on a max of 5-6hrs/day and BOINC suspends/run tasks! (I have 4 other projects) Based on the day I got it - it would have STILL run out of time from the word go!!
It's an AstroPulse v505 5.05 WU.
'ap_01dc06ac_B0_P1_00247_20100206_19920.wu_1'
Should I abort it before even trying..?

I have:
Processor: 2 GenuineIntel Intel(R) Pentium(R) D CPU 2.80GHz [x86 Family 15 Model 4 Stepping 7]
with
NVIDIA GPU 0: GeForce 8800 GT (driver version 19621, CUDA version 3000, compute capability 1.1, 512MB, 381 GFLOPS peak)

The actual crunch time on that host should be (very roughly) about 24 hours, so if BOINC started it now it might make deadline. The huge estimate is probably because your GPU did one or more tasks which took much longer than originally estimated.

Because that Astropulse v505 WU hasn't been started, BOINC must think there's another project which needs the CPU more urgently. Unless you're willing to suspend other projects, I think aborting the WU makes sense.

                                                            Joe

[/quote]
The actual crunch time on that host should be (very roughly) about 24 hours, so if BOINC started it now it might make deadline. The huge estimate is probably because your GPU did one or more tasks which took much longer than originally estimated.

Because that Astropulse v505 WU hasn't been started, BOINC must think there's another project which needs the CPU more urgently. Unless you're willing to suspend other projects, I think aborting the WU makes sense.

                                                            Joe

[/quote]

Now you make me curious, I'll leave it just to see what it does do seeing as it has 4 days till deadline and is due to start... A pair of Seti's have just finished and its working on a pair of Milkways@, with a Milkyway ahead of it.
:-)

---

The actual crunch time on that host should be (very roughly) about 24 hours, so if BOINC started it now it might make deadline. The huge estimate is probably because your GPU did one or more tasks which took much longer than originally estimated.

Because that Astropulse v505 WU hasn't been started, BOINC must think there's another project which needs the CPU more urgently. Unless you're willing to suspend other projects, I think aborting the WU makes sense.

                                                            Joe

Now you make me curious, I'll leave it just to see what it does do seeing as it has 4 days till deadline and is due to start... A pair of Seti's have just finished and its working on a pair of Milkways@, with a Milkyway ahead of it.
:-)

I guess BOINC isn't to concerned about the amount of time it thinks that will take. I wouldn't have thought that it would start something like that sooner, but that shows just how complex the scheduling is on BOINC. It's not going to work right every time I guess.
I'd leave it just to see what happens myself.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[