Just had a look at the work in my cache on my AMD tbird 1,2ghz. The normal reported time to complete is 5.23:37, which I assume is the time for what we could call a 0.417 wu in classic terms.

Earlier today I got 2 wu's uploaded where the reported time to complete is 32.21:44 hours. Strange I thought and looked at data itself in the wu, and found the angle range on both to be 5.680, meaning a VERY fast wu in classic terms.

This gotta be some sort of bug in boinc, or am I totally missing something here !!

I was about to ask the same thing. My amd 2400 usually requires about 3 hours, but I have 2 WU's that will take me 17 hours.
ttyl
Jeff

I have 3 WUs that show a competion time of 24:01:59 whats up with that ;o)
Seti@Home, it is really about the science, isn’t it!!

I don't know if this will help or not, but it's worth trying anyway.

Make sure NOTHING is running on your system except the SETI/BOINC client.
Try to shut down everything in the system tray, too.

Then open the BOINC gui and select the "message" tab.

Now, under the "File" menu, select "Run Benchmarks",
and then do ABSOLUTELY NOTHING, not even moving the mouse
around, until it reports that the Benchmarks have finished.
It will take ONE FULL MINUTE to run, then it will report
the results.

Next, go to the "Project" tab, right-click on the project,
and select "Update". This will send the benchmark results
to the server.

Now, if this actually did anything at all, it MIGHT cause
the BOINC gui to recalculate the "completion time" for the
WUs you already have. I believe it will definitely make
the "completion time" for any more WUs you get look correct.

It's also possible the problem is really just something in
the new splitters and they are estimating very wrongly.
I wouldn't worry too much either way. The estimated time
will NOT affect the ACTUAL time required for a WU. And
the estimated completion time while a WU is running is so
terribly far out of line with reality that it doesn't really
matter until it says it's over 80% done.

The benchmarks arent the problem, there are just some very large wu's. the same thing happened to me everynow and then in classic seti. i am not worried or bothered by it. its just weird to have 40 wu's at 3 hours, and 2 at 17 hours.
ttyl
Jeff

> The benchmarks arent the problem, there are just some very large wu's. the
> same thing happened to me everynow and then in classic seti. i am not worried
> or bothered by it. its just weird to have 40 wu's at 3 hours, and 2 at 17
> hours.

But the OP's post said that WUs that were SHORT in ClassicSeti are now showing up as very long. So in his case, it's "not normal".

My 1st 24 hr WU is running and it is strange, 60% complete, cpu time 25 min, to complete time 16 min, now the time to complete time is getting larger, I think it is figuring out it needs more time, just not 24 plus hrs heh. Running preditor at the same time or the reattachement yesterday may have something to do with it. I know they will figure it out ....
Seti@Home, it is really about the science, isn’t it!!

> My 1st 24 hr WU is running and it is strange, 60% complete, cpu time 25 min,
> to complete time 16 min, now the time to complete time is getting larger, I
> think it is figuring out it needs more time, just not 24 plus hrs heh. Running
> preditor at the same time or the reattachement yesterday may have something to
> do with it. I know they will figure it out ....

all of them do that... it runs the first 50% or so in like 3 minutes, and then from there calculates how much time remaining.
ttyl
Jeff