I clicked to show all tasks and noticed about 1/2 my CPU tasks have a completion time of 50:36 and the other half are at 63:39:39. They are all setiathome_enhanced 6.03 . Seems a bit odd to me, wish they would do away with it, or tone it WAY down...

---

Official Abuser of Boinc Buttons...
And no good credit hound!

I clicked to show all tasks and noticed about 1/2 my CPU tasks have a completion time of 50:36 and the other half are at 63:39:39. They are all setiathome_enhanced 6.03 . Seems a bit odd to me, wish they would do away with it, or tone it WAY down...

I'm seeing this too. The times aren't that high for me though. They're more like 50 minutes to 7 hours.

Although they still seem to complete all in about 2-3 hours regardless of their estimated. I was thinking maybe it could be related to the way the estimation works now, i remember seeing Richard say it may take up to 300+ tasks before the estimation becomes somewhat stable.

---

- Jarryd

I had ests. from the same "tape" as 5:xx:xx and 145:xx:xx for the same computer. Because of the latter, I couldn't get any WUs for days before the current "3"-day outage.

I think the system is really bollixed up, and the crunching is going to be screwed up for a very long time - weeks, maybe. Unless, of course, the Monster Ego who made the changes to the server side relents, and goes back to the older server-side code.

---

I had ests. from the same "tape" as 5:xx:xx and 145:xx:xx for the same computer. Because of the latter, I couldn't get any WUs for days before the current "3"-day outage.

I think the system is really bollixed up, and the crunching is going to be screwed up for a very long time - weeks, maybe. Unless, of course, the Monster Ego who made the changes to the server side relents, and goes back to the older server-side code.

Of course going back to the old code would fix a few things, although i disagree that it's the best option. Lets hope with this new outage schedule we can get all the bugs worked out and the servers running in a decent manner. :)

---

- Jarryd

I have still the flops entries in my app_info.xml file and all estimates are fine.
AFAIK, current the server flops are disabled again.

If they will be enabled again, I need to look if still buggy (not interact well with ReSchedule tool) and if then I need to adjust the values in my app_info.xml file.

---

It's anybody's guess what the Boinc code is going to be like when the servers come back up....
We got no notice when the bomb was dropped on us the last time, and I suspect we will have no notice other than by empirical evidence of our own discovery when 'corrections' have been made.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

It's anybody's guess what the Boinc code is going to be like when the servers come back up....
We got no notice when the bomb was dropped on us the last time, and I suspect we will have no notice other than by empirical evidence of our own discovery when 'corrections' have been made.

Amen, brother!!!!!

---

I clicked to show all tasks and noticed about 1/2 my CPU tasks have a completion time of 50:36 and the other half are at 63:39:39. They are all setiathome_enhanced 6.03 . Seems a bit odd to me, wish they would do away with it, or tone it WAY down...

If that's host 5185924, the "in progress" tasks listed show sent dates from before, during and after the period estimates were being adjusted server-side. I expect it has actually done much of that work during the outage, but having a 1:75 ratio of estimates implies there's still a mix.

The original estimates from the splitter can vary over a 1:5 range depending on AR. The transition to server-side adjustment should have caused another 1:5, yielding 1:25. But since the averaging for anonymous platform was "messed up" there's another factor of 3 in there someplace, and that could be even worse on some hosts.

                                                                  Joe