After this server outage, how many people do you think are going to raise their cache sizes by a large amount, and will this cause a vicious circle by taking all the wu's and leaving no more to dl.
I would like to hear some opinions. Thanks

i have at General preferences
Keep enough work on disk to last between 15 and 15 days
[/url] [/url]
Ich höre immer gerne zu,wenn ich auch nicht immer belehrt werden möchte ;-)

so this server outage didnt get you at all. I know i went over 16 hours without work, and am sure some went longer. on the bright side, cpu temp dropped by a big amount while it was idle.
thanks for the input guido.

Guido:


Could you PLEASE stop inundating the boards and posts with those pics??? Gee, I wonder why the server has so many problems???



Ranz

Hi Bill,

I haven't changed my prefs. I have received one WU of 53 hours to completion. I guess there won't be any left when I'm done processing it...in 5 hours.

Regarding Guido's pictures it's a waste of time asking him to stop. I think we all tried to make him understand but he just keep on going. D'ont know the right term in english but you will understand, It goes into one ear and gets out from the other.

Best regards
Marc

> Hi Bill,
>
> I haven't changed my prefs. I have received one WU of 53 hours to completion.
> I guess there won't be any left when I'm done processing it...in 5 hours.
>
> Regarding Guido's pictures it's a waste of time asking him to stop. I think we
> all tried to make him understand but he just keep on going. D'ont know the
> right term in english but you will understand, It goes into one ear and gets
> out from the other.
>
> Best regards
> Marc
>
>
Thanks Marc, I also left my prefs set at .1 - .7 for a faster turn around of wu's, so i will not hold up the credit process for someone by leaving them in cache for a week or so.

> i have at General preferences
> Keep enough work on disk to last between 15 and 15 days
>
And after 15 days, ALL of your WUs will be past deadline.

Hi

John this is wrong, sorry.

Since the cli show 18 houres for one unit you be give WUs divided by 6.
So when you want to cache for six days you need 8x6 WUs so you have to set 6x6 =49 days.

greetz Mike

The work estimates are being reverted back to their launch day estimates today, we should start to see them show up in the workunit pool very soon.

----- Rom
BOINC Development Team, U.C. Berkeley

Oooooh Goodie!!!

Wonder what that will do to my cache.

> The work estimates are being reverted back to their launch day estimates
> today, we should start to see them show up in the workunit pool very soon.

Lucky me, I got 2 a few hours ago :) Since then it's been the old 6 timers again though.

What exactly was the reason for artificial 6x hike in the estimates? Assuming it was done deliberately?

Mark

> > The work estimates are being reverted back to their launch day estimates
> > today, we should start to see them show up in the workunit pool very
> soon.
>
> Lucky me, I got 2 a few hours ago :) Since then it's been the old 6 timers
> again though.
>
> What exactly was the reason for artificial 6x hike in the estimates? Assuming
> it was done deliberately?
>
> Mark
>
One of the deveopers had some machines that were taking 6x the estimated time, and that developer took it upon themselves to fix the estimates. At least that is what was passed around on the Alpha mailing list.

> The work estimates are being reverted back to their launch day estimates
> today, we should start to see them show up in the workunit pool very soon.
>
> ----- Rom
> BOINC Development Team, U.C. Berkeley
>
>

Thanks for the update, Rom! Do you know why the times were hiked up in the first place?

------------------------------------------------------
We are Borgholio. You will be assimilated...bunghole!

> Thanks for the update, Rom! Do you know why the times were hiked up in the
> first place?
>

My guess is they were hiked up to take into account the bug tracking code that was in BOINC Beta. Back in BOINC Beta there was extensive code that slowed down the processing. Now that were out the code has been taken out, but the estimates have not changed.

In anycase its a mute point, as the work units coming out soon will be adjusted. *yay*

*tip of the hat*

Thanks Rom.
<p align="center">

Click on the banner to view our team (have a look at our Extended BOINC Stats)</p>

> After this server outage, how many people do you think are going to raise
> their cache sizes by a large amount, and will this cause a vicious circle by
> taking all the wu's and leaving no more to dl.
> I would like to hear some opinions. Thanks
>
>

The 'time to completion' estimate is pretty inaccurate to start with. On a 2.4ghz P4, I get 26 hour estimates but finish the WU's in about 5 hours. Therefore, if I keep my cache at .1-3 days, I actually only have enough work for about 10 hours.

Keeping my cache at 4-7 days seems to be the sweet spot for a PC like this - you'll have to play with your settings to accomodate PC's with older CPU's since the completion time estimate is based on the BOINC CPU benchmarks. Hope this helps.

<a>

Hi

For now i set to 6 and 6 days and got more than 30 WUs.

greetz Mike

> The 'time to completion' estimate is pretty inaccurate to start with. On a
> 2.4ghz P4, I get 26 hour estimates but finish the WU's in about 5 hours.
> Therefore, if I keep my cache at .1-3 days, I actually only have enough work
> for about 10 hours.

5 hours is the time needed for my Preserio 2800 laptop P4M 1.4 GHz
512 RAM PC2100 - 400 FSB to complete one WU.

I would have guess that a P4 2.4 would have been faster !?
What could be the cause for this ? Bus speed, RAM speed.

I'm just curious. As for tha thread I've already reply to Bill.

Thanks
Best regards
Marc

> > The 'time to completion' estimate is pretty inaccurate to start with. On
> a
> > 2.4ghz P4, I get 26 hour estimates but finish the WU's in about 5 hours.
> > Therefore, if I keep my cache at .1-3 days, I actually only have enough
> work
> > for about 10 hours.
>
> 5 hours is the time needed for my Preserio 2800 laptop P4M 1.4 GHz
> 512 RAM PC2100 - 400 FSB to complete one WU.
>
> I would have guess that a P4 2.4 would have been faster !?
> What could be the cause for this ? Bus speed, RAM speed.
>
> I'm just curious. As for tha thread I've already reply to Bill.
>
> Thanks
> Best regards
> Marc
>
>

To be honest, it may be faster. I don't really watch it that close. As for RAM speed, every PC I have seems to have the exact same speed - benchmarks show 953.67 MB/sec for my 3.2Ghz HT 1Gb RAM laptop and my 200mhz 256Mb EDO RAM PC. Meh.

<a>

He said in another thread that a developer did try to fix some bug with certain clients or something to that effect. I don't remember exactly which thread it was, but if you click his name you can find all the posts hes written and find it pretty easily.

Chris


> Thanks for the update, Rom! Do you know why the times were hiked up in the
> first place?
>
> ------------------------------------------------------
> We are Borgholio. You will be assimilated...bunghole!
>

Well, the "fix" didn't last very long. For the last day I've been receiving those 6X completion estimate errors again on the new WU's that have been downloaded. When will this really be fixed???

(By the way, it's not a "result" until it's been processed. What we receive is raw data - a Work Unit. When that raw data has been processed, it produces a "result", which is the output that we return. Using the term "result" for unprocesssed raw data is confusing.)

(And the erroneous 6X completion estimates are downright annoying.)

--Bill