I just noticed that the credit for a work unit has been reduced from 420 points to 400 points. It would be nice to get an explanation for that.

Best regards
Berthold

I just noticed that the credit for a work unit has been reduced from 420 points to 400 points. It would be nice to get an explanation for that.

Best regards
Berthold

Credits are based on average run times. The WUs in the newer dataset run faster (ratio of the run times is 400/420).

Hi

I'm currently getting 194 credit per task with high variability, from 40mn up to almost 5 hours.....



It's a bit sad.

Eric beat me to it- i was just about to suggest an increase in Credit due to the increased processing time for the new Tasks and decided to check my results- but Eric's already bumped up the Credit per Task to offset the increased runtime.
Nice work, thank you.

---

Grant
Darwin NT, Australia.

Has anyone else noticed a drop in their RAC over the last 2 days?

As far as a i can tell, run times are unchanged, Credit per Task is unchanged, Estimated completion times are around the same, but the RAC on both of my systems has dropped by roughly 5,000 on one and 4,000 on the other (roughly the same percentage drop on both).
RAC was pretty much steady up to the 30/4, then since the 1/5 the drop.

---

Grant
Darwin NT, Australia.

Has anyone else noticed a drop in their RAC over the last 2 days?

As far as a i can tell, run times are unchanged, Credit per Task is unchanged, Estimated completion times are around the same, but the RAC on both of my systems has dropped by roughly 5,000 on one and 4,000 on the other (roughly the same percentage drop on both).
RAC was pretty much steady up to the 30/4, then since the 1/5 the drop.

I haven't looked at my RAC so I don't know if it's dropped. But there was a power outage on April 30th at the building housing the server and it took about 5 hours to restore. I keep about a days worth of tasks on my computers so I had plenty of work during the outage. If you only keep an hour or two of tasks then you may have run out of tasks and that would have affected your RAC.

I also noticed the ETA on the batch status page went up .2 days (~5 hours) - much of that was recovered when users eventually returned the backlog of results, but it didn't completely recover, possibly because some users were starved of tasks during the outage (but there could be other explanations).

I haven't looked at my RAC so I don't know if it's dropped. But there was a power outage on April 30th at the building housing the server and it took about 5 hours to restore.

That would explain it.
I only keep a small cache (less than 2hrs). One system was down for 45min or so to fix a noisy radiator fan, so i was expecting a slight drop on that one, but was surprised when there was a noticeable drop on both.
But with a 5hr server outage, and the increasing backoffs that occur when BOINC can't contact a project server, the systems could have easily been out of work for 8 hours (or more). This morning i noticed that the RAC is starting to climb again, so the server outage does explain the hiccup.

---

Grant
Darwin NT, Australia.