After a Google search of "how to determine CPU flop count", some time doing research and testing, this was not a consistent way to judge computer performance. With such a wide variance in calculating FLOPS to award credit for work preformed, a slower computer could get more credit than a faster computer. So the best way would be to make all work units the same size, calculate the flops for the work unit and award credit for this calculation. No matter how fast, or slow, the computation was, credit would be the same. This is the best and most fair solution. I think this is being done by some project already. My two cents worth.

I'm sorry, my GPU credits have been going down hill since the last server crash.
My peak with two 4850's on this machine was a little over 90K and still had a very steep climbing slope. Then the crash hit and it is now leveling off at mid 70K.

You started Collatz on September 19, 2009. Other GPU users are notating problems with the two projects playing together.

According to the graph at BOINCStats for your host, looking back across 60 days it becomes plainly clear that your credit per day stayed relatively stable or went up on that host post-cut (09/11 was the date of the cut). The average amount from 09/05/2009 to 09/19/2009 looks to be in the range of 94k - 104k, which includes post-cut rates. Once you started mingling Collatz into the mix, the rates went down. Additionally there have been work availability issues and some bad tasks here and there.

To state that your credit production has dropped within this project is accurate, but doesn't tell the whole story. Had you been getting the same stream of work as before, not mixing another project in, it would've been higher, just like it was during the 09/11/2009 - 09/19/2009 time period, which was after the cut was implemented.

Meanwhile, CPU users generally only come to within 80% of pre-cut rates.

The stats are the stats, and the stats tell the same general story time and time again... CPU users took the brunt of the cut. Period.

While I am not a 'credit whore' when a project constantly cuts back on allotted credit vs run time it does put me off a bit.

...and those of us CPU-only folks are the people bearing the brunt of that credit cut, not those of you with GPUs. You can check that out with your own hosts, particularly the Pentium D. In fact, it appears as though the GPU users credit rates stayed constant or went up some. Your RAC "dropping" is merely due to work fetch issues. If you had a steady stream of work, your RAC would actually be higher now, while those of us with CPU-only systems would still be lower.

The power users like to see their credits soaring and get frustrated at having to constantly switch between different projects to achieve that.

Another aspect of that is those of us who are NOT "power users", who are indeed here because it's the project we are choosing to support, are getting a wee bit tired of various things.......

This what the server page says now!
feeder milkyway Not Running
transitioner milkyway Not Running
milkyway_purge milkyway Not Running
milkyway_av milkyway Not Running
file_deleter milkyway Not Running
Hope its Travis doing updates or something of that sort.
;-p

So move then, Beserk, and stop clogging up this board whingeing about it.

i moved on days ago.

And get even LESS credit. Talk about cutting your nose off to spite you face....go figure.

>You give out a 5000 sec long work unit
Try CPDN - 4,000 hour WUs available there.

Looks like the server is getting lower and lower on wu..

My computers are screaming feed me Leroy..Smile.

Try another Boinc version. That gives a lot of users problems. It doesn't request work right.

Is Boinc or MW suspended?

never mind I got it worked out somehow... just don't ask me to explain it...

Apo wiporepoleposs liponk bepotwepoepon thepo twopo? :Ppo