Mark,

I think so. One of my machines downloaded about 10 tasks, on top of 250, and the reported queue went from 10 days to 44. I don't have the fastest cuda card so, tasks were listed from 23 min to 2 hours. The last one I received is listed at 19.5 hours.

This change is a pitiful disaster. (my opinion)

---

Dave

Mark,

I think so. One of my machines downloaded about 10 tasks, on top of 250, and the reported queue went from 10 days to 44. I don't have the fastest cuda card so, tasks were listed from 23 min to 2 hours. The last one I received is listed at 19.5 hours.

This change is a pitiful disaster. (my opinion)

I dunno if it's a disaster yet.....but it sure is gonna be a painful adjustment period for many.
I still myself fail to understand the point of the exercise.....
Just to see if Boinc can cope with it?

The kitties will claw their way though the rubble, as usual....LOL.

---

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

I made a warm reset of the project.
I copied after all DLed WUs again in the project folder.
So no WU gone lost.

So after ~ 1/2 day..
CPU and GPU WUs have ~ same estimated times.
10 day WU cache set.
CPU WUs for 10+, GPU WUs for ~ 1 day again in BOINC displayed.
BOINC don't ask currently for new WUs.
[EDIT: (But a lot unused/unassigned WUs still in the project folder.)]

Maybe this new changeset run well for stock project, but not for app_info.xml user.

If there will not come a new changeset, I will insert again <flops>.


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

If I understand Joe's analysis, it will NEVER straighten out for mixed mode (GPU, CPU,MB,AP) crunchers. Not something pretty to look forward to.

---

Dave

If I understand Joe's analysis, it will NEVER straighten out for mixed mode (GPU, CPU,MB,AP) crunchers. Not something pretty to look forward to.

I hope that is not true, otherwise DA has once again shown a bit of a dis to the anonymous platform and all that it has contributed to this project.

---

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

Well, I am seeing a bit of a chink in the Cricket graph already.....
Looks like the bogus completion estimates may be fooling most of the Boincs on the project that their computers don't need any more work.

Which is where the fun is really going to start.

Before this server change, my GTX 470 was running, and estimating, shorties as 92 seconds, with a DCF of 0.88

After the server change, new shorty work was estimated at 7660 seconds - 83 times longer. Once I've crunched through a few of those, my DCF will be down to 0.01, and estimate/reality will be back in synch.

Now suppose that the change is reversed, as we're requesting. New work downloaded will be estimated at one second. I run a 12 hour SETI cache on that box (one day, two projects). It's still going to try and download forty thousand shorties.

I suggest people get ready to hit the NNT button.....

I am with you on the I don't understand what issue was addressed with this change. See my post about mixed mode machines (GPU, CPU MB & AP) all with correct estimates.

WHAT DID WE FIX ??

---

Dave

Well, I am seeing a bit of a chink in the Cricket graph already.....
Looks like the bogus completion estimates may be fooling most of the Boincs on the project that their computers don't need any more work.

Which is where the fun is really going to start.

Before this server change, my GTX 470 was running, and estimating, shorties as 92 seconds, with a DCF of 0.88

After the server change, new shorty work was estimated at 7660 seconds - 83 times longer. Once I've crunched through a few of those, my DCF will be down to 0.01, and estimate/reality will be back in synch.

Now suppose that the change is reversed, as we're requesting. New work downloaded will be estimated at one second. I run a 12 hour SETI cache on that box (one day, two projects). It's still going to try and download forty thousand shorties.

I suggest people get ready to hit the NNT button.....

Richard....and I don't really mean to be rude to anybody...
But what is the intended point of this?? I missed it, I guess.

---

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

I suggest people get ready to hit the NNT button.....

That's assuming people are able to get work.
One of my systems (the one with v6.12.33) has run out of GPU work, so each time it misses a request the backoof becomes something completely ridiculous. And since the server is issuing "No tasks sent" most of the time, i don't think there's much chance of me getting any GPU work for that system till the weekend when i can sit there & edit the client_state file & hit "retry" 100s of times untill i get a couple of hundred GPU tasks downloaded & running.
Rather annoying.
:-/

---

Grant
Darwin NT

I suggest people get ready to hit the NNT button.....

I have already set NNT, in hopes that someone will pay attention to the outcry and to avoid getting any more screwed up times.

Who knows, it may stay that way if nothing changes.

---

Dave

Now suppose that the change is reversed, as we're requesting. New work downloaded will be estimated at one second. I run a 12 hour SETI cache on that box (one day, two projects). It's still going to try and download forty thousand shorties.

I suggest people get ready to hit the NNT button.....

Richard....and I don't really mean to be rude to anybody...
But what is the intended point of this?? I missed it, I guess.

No good downloading heaps of work if it's just going to end up timing out.

---

Grant
Darwin NT

I notice that the new increased runtime WUs are maked as 6.09 (cuda23) whereas before they were all 6.10 (cuda_fermi).



EDIT- *scratches head*
At least that's the case on one machine, on the other they're still 6.10 (cuda_fermi).
Will have a closer look later on when i'm awake.

No idea what's going on there- the app_info file on the re-branded machine hasn't changed in 3 months.

---

Grant
Darwin NT

I'm not sure that, depending on when (presuming if) DA would correct his "correction", the effect would be that great. I've been running the "new" timing GPU WU's all day, and the estimates for VHAR's are still coming in at 7+ hours, though they finish in 3-4 minutes. I've seen virtually no change in the estimates today. And, to compound the confusion, my DCF on my twin 580 box has actually gone UP, from 1.16 at noon to 1.21 as of now. Oh, and I'm out of GPU work.

---

Now suppose that the change is reversed, as we're requesting. New work downloaded will be estimated at one second. I run a 12 hour SETI cache on that box (one day, two projects). It's still going to try and download forty thousand shorties.

I suggest people get ready to hit the NNT button.....

Richard....and I don't really mean to be rude to anybody...
But what is the intended point of this?? I missed it, I guess.

No good downloading heaps of work if it's just going to end up timing out.

No worries of that at present.
Given the percentage of 'shorties' in the work mix right now and the bandwidth bottleneck, the servers couldn't possible satisfy the requests anyway.

---

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

My machine seems to think I only need 100ish at a time GPU apps due to the huge estimate times.

The good news is, I'm keeping enough work to keep my GPU's humming. Bad new is, no cache at all.

---

Executive Director GPU Users Group Inc. -
brad@gpuug.org

Richard....and I don't really mean to be rude to anybody...
But what is the intended point of this?? I missed it, I guess.

Hang on while I go and find the threads.

It was a very real, but rare, problem reported and discussed on these boards. It was passed on, in good faith, to the developers by one of our regular messenger pigeons.

A fix was written into the server code. Other eyes spotted problems with it, but their sage advice was ignored. It appears - though none of us have access to the inner workings to confirm this - that the supposed 'fix' was deployed by persons unknown during Tuesday maintenance.

My machine seems to think I only need 100ish at a time GPU apps due to the huge estimate times.

The good news is, I'm keeping enough work to keep my GPU's humming. Bad new is, no cache at all.

How would you get anything cached when Boinc is being told a 2 minute WUs is gonna take an hour and a half when downloaded???

---

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

Richard....and I don't really mean to be rude to anybody...
But what is the intended point of this?? I missed it, I guess.

Hang on while I go and find the threads.

It was a very real, but rare, problem reported and discussed on these boards. It was passed on, in good faith, to the developers by one of our regular messenger pigeons.

A fix was written into the server code. Other eyes spotted problems with it, but their sage advice was ignored. It appears - though none of us have access to the inner workings to confirm this - that the supposed 'fix' was deployed by persons unknown during Tuesday maintenance.

So much for 'good faith'....LOL.

---

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

Weird stuff is beginning to happen. The 19.5 hour GPU I spoke of a few posts back has been recalculated and is now listed as 1 day 3.5 hours. At the same time, this is the machine that an hour ago had a 44 day queue now has a 26.5 day queue. Machine is also beginning to thrash, start a task, abandon it a few minutes later to start another one, neither of which are near deadline.

---

Dave

No, this was a question of me.. ;-)


BTW, I'm confused that this new changeset wasn't tested before at S@h Beta Test.


[EDIT: Sorry, english is not my mother language. I had for a long time only a few years in school.. ;-)]


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

This is a BOINC change, Seti Beta is for testing Seti applications, although there is nothing to stop Dr.A doing tests at SetiBeta. It is not wise to cloud the issues of the testing at Beta, with possible errors introduced by changes to BOINC.

When testing the KISS principle should always be used.

KISS is the acronym for "Keep It Simple, Stupid".