Anyone know about how many credits/hour this is giving out at present? I'll confess: I'm a cobblestone collector (though the right project trumps numbers). DistRTGen, e.g., hands out c. 90/hour (no joke- it's a flat 1080 for each WU, at about 12 hours each). And how do you determine the amount? Thanks, cesium...

I am running two AMD Phenom II computers, a 955 X4 and an 1090T X6, both running Linux Fedora 16 X64 bit.

My faster machine (slightly over clocked X6) actually gets the lower credit.
It has done 8 WUs but only 3 have been validated so far.
I get an average of 42,383.63 seconds (11.77 Hours) with an average of 220.98 credits giving 18.77 Credits per Hour.

The X4 has had 12 validated so an average of 41,354.68 seconds (11.48 Hours) with an average of 243.05 credits giving 21.17 Credits per Hour.

Not sure why there is such a difference in the awarded credit per WU (perhaps the different parties I have been paired with), however overall the credit is quite low.
For almost 12 hours of processing I would of thought I would get more for each WU, so it is not a huge return but it is better than say LHC, though not by much.

Conan

Thank you, Conan... one of these days I'll have to figure out how each DC project sets its own credit, and why there is no average time/credit standard... if one project gives out so much for so many flops used, why not all...
____________
The babydoll in my avatar is Hayley Westenra, the finest soprano on the face of this planet or any other...

I'm getting only 12 credits per hour :(

Many will agree that in order to attract more users, a project needs to grant above-average credits, and if this sparks a credit war among other projects then so be it.
____________
The biggest threat to public safety and security is not terrorism, it is Government abuse of authority.
Bitcoin Donations: 1Le52kWoLz42fjfappoBmyg73oyvejKBR3

Going on what I am getting at the moment, an increase in credit won't spark any credit wars, as it is on the low end for granted credit at the moment.

Conan

The credits (80/WU) are still very low...

Anything around 120-150 credits would be fine for 6 hours of CPU time. Thank you.

After having a (very) quick look at some of my results from the last batch and this batch, I can see that the average per hour has gone up.

In the last batch with the longer work units I grabbed 8 work units (4 longest running and 4 shortest running) for and average runtime of 11.78 hours (94.24 hours total).
These generated 2,018.12 points for and average of 21.42 credits per hour.

Did the same with the latest batch and got an average runtime of 3.22 hours (25.78 hours total).
Generating 640 points (at 80 per WU), for an average of 24.83 credits per hour.

(I have taken out my very highest and very lowest from both lots of figures as I consider them outliers to the average of most of my results. My lowest in the last batch was 15.86 cr/h and the highest was 24.30 cr/h, with the latest batch it was 18.36 cr/h and 27.25 cr/h).

At 80 per Work Unit on my 8 WU average I get an average of around 24.83 cr/h.
At 90 per Work Unit I would get 720/25.78 = 27.93 cr/h.
At 95 per Work Unit I would get 760/25.78 = 29.48 cr/h.
At 100 per Work Unit I would get 800/25.78 = 31.03 cr/h.
At 105 per Work Unit I would get 840/25.78 = 32.58 cr/h.
At 110 per Work Unit I would get 880/25.78 = 34.14 cr/h.
At 115 per Work Unit I would get 920/25.78 = 35.69 cr/h.
At 120 per Work Unit I would get 960/25.78 = 37.24 cr/h.(Amauri's lowest)
At 150 per Work Unit I would get 1200/25.78= 46.55 cr/h.(Amauri's highest)

From this I believe the 150 per work unit would be too high.
With 90 not a lot better than 80.

Between 100 and 120 I would be very happy with.

Conan

(I can do a better analysis if need be using more results, but run times are fairly even so it wont really change much)

Did the same with the latest batch and got an average runtime of 3.22 hours (25.78 hours total).
Generating 640 points (at 80 per WU), for an average of 24.83 credits per hour.

Did the same with the latest batch and got an average runtime of 3.22 hours (25.78 hours total).
Generating 640 points (at 80 per WU), for an average of 24.83 credits per hour.

In my computer: 6 tasks completed, average runtime of 5.52 hours, 80 credits/WU, average of 14.49 credits/hour

Please don't assume that your computer is an average computer, there are several configurations elsewhere. There are people with a slower computer than mine.

P.S.: 120 is a good value

Conan, please do not get upset, I did not want to criticize you, I'm sorry. As my English is not good (I speak portuguese), I usually use short sentences, which may seem rude, but it is not my intention.

My concern is that, practically, only the heavy crunchers post in the forums, and the terms of comparison for determining credits are distorted. People with modest computers rarely post on the forums, get discouraged with few credits received and quit running the project.

In my modest computer I run 4 CPU projects and 4 GPU projects. I try to maintain an average of 20 credits / hour for CPU projects, and when a project gives few credits (or even too much credits), I prefer to choose another project.

So let's go crunch and be happy!

No worries Amauri, all OK.

Thanks for that Kyong, much appreciated.

Also thanks for a very well run project.

Conan

Thanks, I have set credit 120 credit/WU.

Got it. Thanks for the quick reply.

I have a curious problem...

My machine doesn't show up in the Top Machines list, but I do show up in the Top Participant list...

Funny...

LOL!

8-)