The Wu's have increased by about 1/3 but the Credit hasn't, right now Milkyway Credit is lower than Collatz or DNETC ... ???

---

STE\/E

The Wu's have increased by about 1/3 but the Credit hasn't, right now Milkyway Credit is lower than Collatz or DNETC ... ???

April Fools?? :(

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

The Wu's have increased by about 1/3 but the Credit hasn't, right now Milkyway Credit is lower than Collatz or DNETC ... ???

I'm seeing a 70% increase in time with no increase in credits. Guess it's time to go to Collatz. Cards run cooler on single precision anyay.

The Wu's have increased by about 1/3 but the Credit hasn't, right now Milkyway Credit is lower than Collatz or DNETC ... ???

I'm seeing a 70% increase in time with no increase in credits. Guess it's time to go to Collatz. Cards run cooler on single precision anyay.

Yep, me too... Collatz bound with everything...

Bye, have fun, see ya later.

NO wait, I am already have a presence there hahaha.

Don't worry team, I am here for the science, so I will stay!
Must admit, haven't seen the old nothing then 140% then count backwards routine for a few weeks now. ~2:37 on the 4 x aircooled 5970's and ~2:20 on the 2 x water cooled ones.

---

Bye, have fun, see ya later.

NO wait, I am already have a presence there hahaha.

Don't worry team, I am here for the science, so I will stay!
Must admit, haven't seen the old nothing then 140% then count backwards routine for a few weeks now. ~2:37 on the 4 x aircooled 5970's and ~2:20 on the 2 x water cooled ones.

Lots of luck. Just checked your time and they've increased to 160 seconds from 108 seconds for the same credits. I believe that's a 48% reduction in effort. Don't take my word, just have a look.

Yep, seeing it here too.
Old WU times ~110s (3.28897e+013 floatingpoint ops on GPU, 2.47165e+008 on FPU)
New WU times ~161s (4.67516e+013 floatingpoint ops on GPU, 3.84156e+008 on FPU)
Same credit.
The new once should give ~305 instead of 213.
:(

First of April is over, so please correct this now.

and we're getting the % going to 140%+ and then counting down. Looks like a weird bunch of WU's and now I cant send work back
perfect
It looks like it cleared

---

Blah blah blah you know the rest

480sec against 327sec before, i.e 47% down

update: 4870 OC'd 850/900, crunching 2WUs simultaneously

---

110 before now 155

---

Blah blah blah you know the rest

New WU times ~161s (4.67516e+013 floatingpoint ops on GPU, 3.84156e+008 on FPU)
Same credit.
The new once should give ~305 instead of 213.

To be correct, the current credit multiplier for double precision operations should be 5.44 credits per calculated Tflop (10^12 flop). That means the WU from your example is worth

46.7516 + 0.0004 TFlop (GPU + CPU)
=> 46.752 TFlop * 5.44 credits/DP-TFlop = 254.33 credits

The last round of optimizations in september last year reduced the amount of necessary operations a bit (hence the speedup around that time), but the project sticked to the old flops count and didn't adapted the new values.

I restarted my rig, got new WUs, now it's OK. Probably, "bad" batch? :-)

---

My jobs seem to have returned to their old run times or very close, so need to run away yet. It may be about earning credits but it should not be all about it, people seem to jump from project to project as soon as they get a few hours of lower production, usually it works itself out and if the discrepancy is big the project usually makes an adjustment before long

---

I restarted my rig, got new WUs, now it's OK. Probably, "bad" batch? :-)

Mine have returned to their normal Times too without rebooting but I think it may have had more to do with Travis messing with the Validator from what I read in another Thread, could be wrong on that though ...

---

STE\/E

New WU times ~161s (4.67516e+013 floatingpoint ops on GPU, 3.84156e+008 on FPU)
Same credit.
The new once should give ~305 instead of 213.

To be correct, the current credit multiplier for double precision operations should be 5.44 credits per calculated Tflop (10^12 flop). That means the WU from your example is worth

46.7516 + 0.0004 TFlop (GPU + CPU)
=> 46.752 TFlop * 5.44 credits/DP-TFlop = 254.33 credits

The last round of optimizations in september last year reduced the amount of necessary operations a bit (hence the speedup around that time), but the project sticked to the old flops count and didn't adapted the new values.

CP, I'm happy with the Credits I get get now but am I reading you right and your saying we should be actually getting more but the Project hasn't raised the Credits to the Level they should be ... ???

---

STE\/E

While I made a rough guess based on the credits for a 'normal' WU, he made a calculation based on the FLOP count of the example I gave.
His results:
The 'normal' WU gives a little bonus for the project hickups and the longer WU has nearly the same % as penalty.