What I got was asses calling people that talk about cross party parity whiners.

If I were a moderator, much of this thread would go as flames.

Please keep personalities out of it.

Having approximately the same credits per hour for a particular host across projects is what is SUPPOSED to happen in BOINC. If people are tired of hearing about this, then please ask the project administrators to get the calculation right rather than being proud of running off people that keep making that claim.

Projects that generate grossly too high credit claims should be removed from the cross project stats sites as this is just a way of stupidly inflating your cross project credit scores.

The long tasks really should be granting about 50 CS per task. Granting more is anti-social of the project administrators. The project administrators should look at what other projects are granting per hour for a particular host and attempt to match that here.

The only thing I've seen to the contrary is if the Computer gets kicked off unexpectedly like when it might lose power for a second during a thunder storm the Wu's will error out most of the time ... :)

...So yes, the extra time spent has a definite value. :)

Oh really! What is that "definite value"? If the computation time is increased by a factor of 30 or 60 (for example), is the "definite value" increased by 30 or 60? And if the computation time is increased by a factor of 30 or 60, the available computing resources (in terms of throughput) for Milky Way have been reduced by a factor of 30 or 60. What is the "definite value" of reducing the computing resources by 30 or 60?

Is the increased accuracy 30 or 60 times more valuable? Seems highly unlikely or the project scientists would have increased the accuracy long ago. That they didn't do so before shows that your so-called "definite value" is small indeed.

A modest increase in accuracy could have been credible. But be clear about what's actually happening here. It's not much about the science. Rather, resources are now being largely wasted and accuracy is being "tuned" in order to relieve pressure on the server. There's little "definite value" in that.

My antique Powermac G4 has taken 14 hours to get 20% through a WU; at this rate, it will never finish the queued WU's that used to take only 20 minutes each.

My speedy dual-core PC, on the other hand, whips through each in only 5 hours.

Looks like I'll have to switch my Mac to another BOINC project.

I wouldn't say it's necessary to drop MW from the Mac. Once BOINC adjusts itself to the new run times, it will likely only download one or two tasks at a time. This process will be complete much quicker if the project admins change the estimated run time on the WU's, but BOINC is capable of adjusting for itself even if they don't. When you get WU's that are nearly past deadline, just abort them and the computer should download 1 or 2 tasks and you'll be good.

Hi,

Apparently you perfer gestapoism to democracy...

The golden Godwin of the day goes to JRenkar ...

Regards,
Carsten

Old ones were 2:30, new ones are as well 2:30. Only the for the old ones it was minutes, for the new ones it's hours. So the same her as with niterobin.

What's the nearly same as well is the ridiculous amount of credits that gets tossed after completed ones, on the first one here even 10% more. One third to one quarter should be enough.

Thank you for the information it is greatly appreciated.

I'm not sure that I'll be able to get through all of the WUs that were downloaded resently since the size has changed but no change to the amount of time to complete stayed the same. I received about 15 WUs and I don't know if the given deadline will be enough time to get through all of them. When they were downloaded the estimated time for my computer was 6 mins 47 secs. I'm currently at 1 hour 41 mins and the estimated time to completion is at 1 hour 21 mins and still is counting upward.

Again thank you for your help,

Warren Rogers

I am just happy that the ul/dl here stopped jamming my system and I can crunch again.....for now.

Not jamming my systems either, mainly because I'm not getting any new work ... LOL