super charged?

There is something going on apparently. Normally my daily granted credit varies between 2.2-2.5 Million but for the last 3 days, i have exceeded 4 Million per day.
Could it be that the new SSE2 CPU applications reduce the pending credits? Anyone with another idea?

Anyone with another idea?

All my completed tasks appear to be taking the same time and granted the same credit as before the credits started to rain down. However, my daily credit increase (based on BOINCstats) is about 3 times normal.

I'm trying not to get used to this and am waiting for what I'm afraid is an inevitable "correction". :D

---

Anyone with another idea?

All my completed tasks appear to be taking the same time and granted the same credit as before the credits started to rain down. However, my daily credit increase (based on BOINCstats) is about 3 times normal.

I'm trying not to get used to this and am waiting for what I'm afraid is an inevitable "correction". :D

I don't think there can be a correction to this because if there is an error in crediting, it will be hard to accurately remove the extra credits, considering what has been happening has already happened. (what a tense there:))

what's the line from the movie, business is a boOMING!

I assume the admin are all over this, so that we are now on the third day begs questions about the source. I like credit, but, another line from a movie, not like this. 2-3x what we crunch?

this is becoming a boatload-of-credit BOON!, cousin.

sorry.

Anyone with another idea?

All my completed tasks appear to be taking the same time and granted the same credit as before the credits started to rain down. However, my daily credit increase (based on BOINCstats) is about 3 times normal.

I'm trying not to get used to this and am waiting for what I'm afraid is an inevitable "correction". :D

I don't think there can be a correction to this because if there is an error in crediting, it will be hard to accurately remove the extra credits, considering what has been happening has already happened. (what a tense there:))

I think it would be hard to correct too. It seems random the amount that is granted. As well as the millions of tasks done each day. The times for mine have been from most running normal to a few up to 20% longer.

---

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

Anyone with another idea?

All my completed tasks appear to be taking the same time and granted the same credit as before the credits started to rain down. However, my daily credit increase (based on BOINCstats) is about 3 times normal.

I'm trying not to get used to this and am waiting for what I'm afraid is an inevitable "correction". :D

I don't think there can be a correction to this because if there is an error in crediting, it will be hard to accurately remove the extra credits, considering what has been happening has already happened. (what a tense there:))

I think it would be hard to correct too. It seems random the amount that is granted. As well as the millions of tasks done each day. The times for mine have been from most running normal to a few up to 20% longer.

as someone pointed out: the WUs are crunching normal times with same credit assigned each as before. so a normalizing tally could be as easy as a script that rips through each account for what they did (actual) for selected span. this assumes WU info kept long enough to cover however long this goes. at the minimum and desperate, a procrustean chop of .5 daily would provide a fit minimizing damage though not accurately; I am getting more than 2x.

the big question: what is going on?


it would be nice to get word from the crew with the view.

Something needs to happen - and quickly. Its got to the stupid level now, its gone on too long, and its effect on the whole BOINC community is now tangible. Its clear its something to do with the credit calculation at server level as the time taken to crunch and credit awards at the cruncher WU end are unchanged.

Crunchers are tolerant of errors/problems/mistakes, the world is not perfect. However after such a length of time since it was obvious something was dramatically wrong, it does not reflect well on the devs or their understanding of the needs of Crunchers.

Credits may well be worthless, and as such they are, but they play an important part in the whole BOINC mix. To ignore this problem for the length of time it has been, is to send a lofty high handed message "credits dont matter anyway". If its a real complex drama behind all this, fine, the Project should suspend crunching until its resolved.

Whichever way its looked at, either suspend the Project or fix it. To let the situation continue is rediculous.

Regards
Zy

I'm really not quite sure what's going on. Are you guys getting more credit for WUs than you used to?

I'm wondering if maybe there's some kind of server side bug awarding credit for workunits more than once. Anyone have any ideas?

---

I'm really not quite sure what's going on. Are you guys getting more credit for WUs than you used to?

I'm wondering if maybe there's some kind of server side bug awarding credit for workunits more than once. Anyone have any ideas?

Each task shows the correct credit was awarded.

---

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

I'm really not quite sure what's going on. Are you guys getting more credit for WUs than you used to?

I'm wondering if maybe there's some kind of server side bug awarding credit for workunits more than once. Anyone have any ideas?

Each task shows the correct credit was awarded.

Could it just be because we got the scheduler to correctly send out SSE2 applications, which are over twice as fast as the ones without SSE2?

---

All WU's computed as usual. All WU's, that displayed in hosts tasks, take a normal Granted Credit. But Granted Credit for user grows too fast.

I'm really not quite sure what's going on. Are you guys getting more credit for WUs than you used to?

I'm wondering if maybe there's some kind of server side bug awarding credit for workunits more than once. Anyone have any ideas?

Each task shows the correct credit was awarded.

Could it just be because we got the scheduler to correctly send out SSE2 applications, which are over twice as fast as the ones without SSE2?

twice as fast in what sense? maybe I am missing something. It has been posted, so that you know, that our end looks normal, at least for some of us. when we check our completed tasks, as posted on the server, they look the same: same times and same credit as before this began. I am not crunching 2-3x more WUs or see 2-3x more credit per WU. so, the blow-up is happening after crunched WU credit granted as indicated in our tasks.

I'm really not quite sure what's going on. Are you guys getting more credit for WUs than you used to?

I'm wondering if maybe there's some kind of server side bug awarding credit for workunits more than once. Anyone have any ideas?

Each task shows the correct credit was awarded.

Could it just be because we got the scheduler to correctly send out SSE2 applications, which are over twice as fast as the ones without SSE2?

I wish. But I'm seeing the same amount of credit in the same amount of time per wu. I just think somehow the server is granting credit twice.

I'm really not quite sure what's going on. Are you guys getting more credit for WUs than you used to?

I'm wondering if maybe there's some kind of server side bug awarding credit for workunits more than once. Anyone have any ideas?

Each task shows the correct credit was awarded.

Could it just be because we got the scheduler to correctly send out SSE2 applications, which are over twice as fast as the ones without SSE2?

twice as fast in what sense? maybe I am missing something. It has been posted, so that you know, that our end looks normal, at least for some of us. when we check our completed tasks, as posted on the server, they look the same: same times and same credit as before this began. I am not crunching 2-3x more WUs or see 2-3x more credit per WU. so, the blow-up is happening after crunched WU credit granted as indicated in our tasks.

Lovely, that means I have some debugging to do. Hopefully we'll get this resolved soon.

---

I'm really not quite sure what's going on. Are you guys getting more credit for WUs than you used to?

I'm wondering if maybe there's some kind of server side bug awarding credit for workunits more than once. Anyone have any ideas?

Each task shows the correct credit was awarded.

Could it just be because we got the scheduler to correctly send out SSE2 applications, which are over twice as fast as the ones without SSE2?

twice as fast in what sense? maybe I am missing something. It has been posted, so that you know, that our end looks normal, at least for some of us. when we check our completed tasks, as posted on the server, they look the same: same times and same credit as before this began. I am not crunching 2-3x more WUs or see 2-3x more credit per WU. so, the blow-up is happening after crunched WU credit granted as indicated in our tasks.

Lovely, that means I have some debugging to do. Hopefully we'll get this resolved soon.

It's great that you responded, indication the confirmation of awareness:). What kind of procedure will you use to reverse the extra credits? Or will you perform such actions?

I'm really not quite sure what's going on. Are you guys getting more credit for WUs than you used to?

I'm wondering if maybe there's some kind of server side bug awarding credit for workunits more than once. Anyone have any ideas?

Each task shows the correct credit was awarded.

Could it just be because we got the scheduler to correctly send out SSE2 applications, which are over twice as fast as the ones without SSE2?

twice as fast in what sense? maybe I am missing something. It has been posted, so that you know, that our end looks normal, at least for some of us. when we check our completed tasks, as posted on the server, they look the same: same times and same credit as before this began. I am not crunching 2-3x more WUs or see 2-3x more credit per WU. so, the blow-up is happening after crunched WU credit granted as indicated in our tasks.

Lovely, that means I have some debugging to do. Hopefully we'll get this resolved soon.

It's great that you responded, indication the confirmation of awareness:). What kind of procedure will you use to reverse the extra credits? Or will you perform such actions?

Well right now I'm focused on fixing the problem. Chances are I'll just let everyone enjoy the free credits, instead of mucking around in the database and potentially making things even worse.

---

Travis: is some ET of fixing this?

One thing I've noticed:
In the BOINC Manager, percent completed stays at 0% till completion time,then goes above 100% on this type of task for a few extra seconds:
11/10/2010 8:34:30 PM Milkyway@home Starting de_separation_82_2s_40_2_882564_1289403509_0
with the 40
Completion times are normal.
And my average is shooting up.
I think the 30 shows the percentage right.
The 20 is ok too.
I'll try to have a look at the other types.

Regards

---

One thing I've noticed:
In the BOINC Manager, percent completed stays at 0% till completion time,then goes above 100% on this type of task for a few extra seconds:
11/10/2010 8:34:30 PM Milkyway@home Starting de_separation_82_2s_40_2_882564_1289403509_0
with the 40
Completion times are normal.
And my average is shooting up.
I think the 30 shows the percentage right.
The 20 is ok too.
I'll try to have a look at the other types.

Regards

Not on my systems, the _40_ tasks progress normally as do all the others...

-Dave

---

None of my rigs are showing anything unusual, like TGG and others point out.

The WUs seem to be crunching in the expected time and the expected level of credit is being given. But somehow the total credit, and accompanying RAC, is on the up.

---

Go away, I was asleep