Sorry if this is posted elsewhere, I searched and couldn't find it.

Just looked at BOINC and the current BURP task is at .060 complete and has been working for 6 hours on 4 CPUs.

Problem is the deadline is in 12 hours and estimated time to completion is 426 days.

It downloaded the work just before starting.

Question: Should I abort if it won't finish by the deadline?

Just looked at BOINC and the current BURP task is at .060 complete and has been working for 6 hours on 4 CPUs.

Percentage can be quirky and is mostly not fully correct anyway.

Problem is the deadline is in 12 hours and estimated time to completion is 426 days.
...
Question: Should I abort if it won't finish by the deadline?

Don't worry about it, you can finish every task even if it goes over the deadline, you always get credit.

---

Life is Science, and Science rules. To the universe and beyond
Proud member of BOINC@Heidelberg
My BOINC-Stats

Is any one finding WUs from session 3352 are taking a long time to complete?

WU 3211857 has been running for 16hrs here and is now showing first signs of nearing completion. Deadline is less than 2 hours away.....

Is any one finding WUs from session 3352 are taking a long time to complete?

WU 3211857 has been running for 16hrs here and is now showing first signs of nearing completion. Deadline is less than 2 hours away.....

Finished. 18hrs 12mins run time, reported back at 2024 UK time.

I am doing a unit at the moment that says on the project page timed out, no response... yet i am currently 2hrs 40mins into it?!?!?! so not sure what thats all about...

But yes there is alot of tasks i have been sent that i can not complete in time...

I have had a similar situation on this end. 8x2.33Ghz cores (xeon) 24Gigs of RAM, and after processing for 6+ hours it was well under 1% and stated 18+ days for completion.

I aborted that one just in case it was bugged, and it looks like it wasn't. This one is faster, but there is no way any of these are coming back on a 24 hour deadline.

If we get credit for them being past the deadline, no harm in letting them run I guess, but what a surprise it was to see the 18+ day time on there. :-)

---

Our Advice is to support all useful BOINC projects. Smart people needed to give advice to those who seek answers: Give or Get Free Advice Here

I have had a similar situation on this end. 8x2.33Ghz cores (xeon) 24Gigs of RAM, and after processing for 6+ hours it was well under 1% and stated 18+ days for completion.

I aborted that one just in case it was bugged, and it looks like it wasn't. This one is faster, but there is no way any of these are coming back on a 24 hour deadline.

If we get credit for them being past the deadline, no harm in letting them run I guess, but what a surprise it was to see the 18+ day time on there. :-)

Ignore the remaining time, % progress... i have one currently that says 6d 17hrs and going up fast... the WU at an educated guess will finish in just under 2hrs!

I've just dipped my toe into BURP, mostly SETI before, but I'm very disheartened by it and afraid I'm I'm going to have to stop after just two WUs.

I think it's a great idea and I'd love to contribute, but the deadline times are just ridiculous - the task I'm currently getting (the one you're on about I think) you're getting just 18 hours to complete it.

Now OK, my PC is not too slouchy - an older model i7 - it's completed both the tasks I got in a little over 6 hours. BUT I don't generally run my PC 24hrs a day, only about 8-12 hrs while I'm working/playing etc. on it, and also I only run BOINC at 50% CPU usually as the CPU fan can get noisy at more than that and electicity usage goes up as well.

I can run virtually any other BOINC project happily with that - 8 virtual CPUs, so about 40 CPU hours per day on average, but not this project which seems to need at least double that output per day just because of the deadline times.

Please change the deadlines to 3 days instead of 18hrs and I'll happily come back.

---

The deadlines are set to try and get the rendering through as fast as possible, but there is no penalty to the users for completing a task past the deadline. Everyone gets credit for completing it if it's done early, on time, or a week late.

---

Click here to see My Detailed BOINC Stats

That's all very well, but I thought that BOINC generally just abandons WUs when they've passed their deadline.
If, for example, I was running a task for BURP and got to 5hrs completed (only 1 hr to go), shutdown the PC for the night, fired it up again the next day and the deadline time has now passed won't BOINC just abandon the WU - even though there's only 1 hour left to process on it?
If so, then I've just wasted 5 hrs of CPU runtime on my PC that I could have put to other BOINC projects.

---

BOINC only aborts a WU after the deadline if it hasn't actually started processing the WU, so even resuming after the deadline won't get it aborted.

Normally if a WU isn't returned by the deadline, it gets sent to another host. If you return your WU before the resent WU you will still get credit.
It seems that at BURP you get the credit even if the WU is returned after the resent WU. I have seen this today - meaning I'm annoyed with myself for aborting another WU that I thought would not get credit!

The rules are configurable by the project admins; with BURP, the deadlines are more of a suggestion. However, there is one problem with BURP--checkpointing has not been implemented by the Blender team, so if you restart your computer you will lose any progress. So, if you restart your host and the task is past the deadline, yes it will be aborted.

The way around that, would be to use sleep or hibernate when you would otherwise shut down. Then, so long as the task eventually gets completed and returned, you will get credit.

---

Click here to see My Detailed BOINC Stats