I'm not gonna get all philosophical on this but I WAS getting about 9k here (milsop's app.) and now less than 1.5k per day.( new opp app) I'd just like to see a reasonable adjustment.

again, how does that compare to other projects? also if you were using the optimized application on older machines chances are it's not bumping up to near the credit limit anymore, so you're seeing more of a penalty.

I'm running an '03server 3.0 xeon DDR2-400 Ecc Reg's So its a Quad... kinda.

EDIT: Is this about bumping the client or fair credits per cpu?
EDITx2 Sorry I'm not running an i7!

---

A clear conscience is usually the sign of a bad memory

Maybe we need a separate BOINC project to determine how credit should be awarded.

Arion, your calculations surprise me, since for me Einstein gives better credit atm...

Monday I think it was I upgraded to the Power App (in testing) .07, I was using .05 and it seems it has slowed einstein down a bit here in comparison to other workunits I have before the switch over. I'm not sure if I'm hitting the top of a trough. It was 2 workunits that spanned the same amount of time that the ones from MW processed.If I remember right last time I checked it was in the area of .52 or something.

Otherwise were my calculations based on the correct formula?

Edit - I just ran a quick check on pairs of previous ones before I switched over to the latest release on the power app and the average was running around .50 - .52

I'm not gonna get all philosophical on this but I WAS getting about 9k here (milsop's app.) and now less than 1.5k per day.( new opp app) I'd just like to see a reasonable adjustment.

again, how does that compare to other projects? also if you were using the optimized application on older machines chances are it's not bumping up to near the credit limit anymore, so you're seeing more of a penalty.

I'm running an '03server 3.0 xeon DDR2-400 Ecc Reg's So its a Quad... kinda.

EDIT: Is this about bumping the client or fair credits per cpu?
EDITx2 Sorry I'm not running an i7!

and how do the credits awarded from MW compare to other projects?

---

Maybe we need a separate BOINC project to determine how credit should be awarded.

Credit@Home?

Look out for users named "AIG", "FannieMae", or "Citi"...

and how do the credits awarded from MW compare to other projects?

Based on my calculations Travis (only on one system against einstein - NOT Boinc Wide) With Milksap's app I was capped at 108 credits per hour. On Einstein a workunit there takes average 6 1/2 to 8 hours and credit awarded is 222.43.

Now with the new app here it is more reasonable in that I'm getting about 40+ credits per hour. (ballpark). I realize that my figures are only for 1 of my systems - AMD 64 X2 6400 stock and it is not maybe the norm with the majority of other users. I have 3 slower systems that are taking much longer to process at einstein and here.. If I use this as a general example then in relation to Einstein you are a little high BUT not to any kind of extreme. Based on the comparison chart that is being discussed I say you are just above some and a lot lower than others. Is this a fair amount of credits? I don't have any problems but you ultimately make the decision.

To put it in another perspective, I don't think at this point you have to worry about DA paying you another visit. <cough, cough>

---

Maybe we need a separate BOINC project to determine how credit should be awarded.

Credit@Home?

Look out for users named "AIG", "FannieMae", or "Citi"...

Should we look for a bailout if our credits dry up? <Smile>

... nm_stripe86 does more work than nm_stripe79 and nm_stripe82, but it awards more credit based on the extra work. You should be getting more credit for the longer WUs.

Hm, I don't understand it: my nm_stripe86 get less credits: only 21,18 per WU but the nm_stripe79 and nm_stripe82 do get ~39 credits. *scratches head*

---

Lovely greetings, Cori

and how do the credits awarded from MW compare to other projects?

I have just been doing some SETI, to build the RAC slightly, and the claimed and given credit per hour is similar to MW (based on a short 20 Wu run.

... nm_stripe86 does more work than nm_stripe79 and nm_stripe82, but it awards more credit based on the extra work. You should be getting more credit for the longer WUs.

Hm, I don't understand it: my nm_stripe86 get less credits: only 21,18 per WU but the nm_stripe79 and nm_stripe82 do get ~39 credits. *scratches head*

really? stripe_86 should be worth more credits than 79 and 82... the database says stripe 86 should be generating ~42 credits while 79 and 82 are ~39 credits

---

Maybe we need a separate BOINC project to determine how credit should be awarded.

Credit@Home?

Look out for users named "AIG", "FannieMae", or "Citi"...

Should we look for a bailout if our credits dry up? <Smile>

No, it's if their credits dry up. In that situation, Credit@Home will issue them "Credit Bonds" (workunits) while the rest of us note that we keep getting told "There was credit (work) available for other platforms"

... nm_stripe86 does more work than nm_stripe79 and nm_stripe82, but it awards more credit based on the extra work. You should be getting more credit for the longer WUs.

Hm, I don't understand it: my nm_stripe86 get less credits: only 21,18 per WU but the nm_stripe79 and nm_stripe82 do get ~39 credits. *scratches head*

really? stripe_86 should be worth more credits than 79 and 82... the database says stripe 86 should be generating ~42 credits while 79 and 82 are ~39 credits

Hmmm... I have had another look at my results and found a nm_stripe86 with 42 credits but the newer ones get only the half of the credits:

"old" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57002953

"new" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57010436

---

Lovely greetings, Cori

... nm_stripe86 does more work than nm_stripe79 and nm_stripe82, but it awards more credit based on the extra work. You should be getting more credit for the longer WUs.

Hm, I don't understand it: my nm_stripe86 get less credits: only 21,18 per WU but the nm_stripe79 and nm_stripe82 do get ~39 credits. *scratches head*

really? stripe_86 should be worth more credits than 79 and 82... the database says stripe 86 should be generating ~42 credits while 79 and 82 are ~39 credits

Hmmm... I have had another look at my results and found a nm_stripe86 with 42 credits but the newer ones get only the half of the credits:

"old" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57002953

"new" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57010436

I'm seeing this too.

57212793

---

Calm Chaos Forum...Join Calm Chaos Now

... nm_stripe86 does more work than nm_stripe79 and nm_stripe82, but it awards more credit based on the extra work. You should be getting more credit for the longer WUs.

Hm, I don't understand it: my nm_stripe86 get less credits: only 21,18 per WU but the nm_stripe79 and nm_stripe82 do get ~39 credits. *scratches head*

really? stripe_86 should be worth more credits than 79 and 82... the database says stripe 86 should be generating ~42 credits while 79 and 82 are ~39 credits

Hmmm... I have had another look at my results and found a nm_stripe86 with 42 credits but the newer ones get only the half of the credits:

"old" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57002953

"new" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57010436

I'm seeing this too.

57212793

and these are still running longer than the other ones?

---

and these are still running longer than the other ones?

The one with only 21 credits was even a bit longer than the one with 42 credits (see my links). ;)

---

Lovely greetings, Cori

... nm_stripe86 does more work than nm_stripe79 and nm_stripe82, but it awards more credit based on the extra work. You should be getting more credit for the longer WUs.

Hm, I don't understand it: my nm_stripe86 get less credits: only 21,18 per WU but the nm_stripe79 and nm_stripe82 do get ~39 credits. *scratches head*

really? stripe_86 should be worth more credits than 79 and 82... the database says stripe 86 should be generating ~42 credits while 79 and 82 are ~39 credits

Hmmm... I have had another look at my results and found a nm_stripe86 with 42 credits but the newer ones get only the half of the credits:

"old" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57002953

"new" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57010436

I'm seeing this too.

57212793

I actually just checked out the server, in last nights mess the parameter files for stripe86 got cut down in accuracy by half (which explains why they're giving about half less credits). newly generated stripe86 wus should be giving the right credit (and take the typical time).

the ones that were giving less credit should crunch in about half the time, so the crunch time to credit ratio should still be the same.

---

and these are still running longer than the other ones?

I'm starting to see the same thing here.

NM-Strip86-r2 - 2414.85 - 12.57 - 42.33
NM-Strip86-r2 - 2409.74 - 12.54 - 21.18

Description ---/cpu Time-Claimed-Awarded

Travis, will I have to allow computers to be shown if you need to look at them or can you look at my work history without a public flag?

computer ID is #36995



79's and 82's are getting 39.84....

I actually just checked out the server, in last nights mess the parameter files for stripe86 got cut down in accuracy by half (which explains why they're giving about half less credits). newly generated stripe86 wus should be giving the right credit (and take the typical time).

the ones that were giving less credit should crunch in about half the time, so the crunch time to credit ratio should still be the same.

Ok, but at least once there must have been a hiccup:
"old" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57002953 CPU time 3551.474 = Granted credit 42.33592

"new" nm_stripe86: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57010436 CPU time 3741.538 = Granted credit 21.180365

I have seen a newer WU now, where the crunch time is indeed cut in about half time so there the reduced credits do match:
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57012280 CPU time 1765.394 = Granted credit 21.180365

Ok, it seems it was only one WU affected with me, but I tell ya I really got confused at first!! *grin*

---

Lovely greetings, Cori

I'm seeing this too.

57212793

and these are still running longer than the other ones?

Looking at mine, they are running about the same CPU time, ~2500 seconds.

Here is a 42 credit one which ran 2512.03 seconds, the one linked above was a 21 credit WU that ran for 2516.56 seconds.

---

Calm Chaos Forum...Join Calm Chaos Now

I'm seeing this too.

57212793

and these are still running longer than the other ones?

Looking at mine, they are running about the same CPU time, ~2500 seconds.

Here is a 42 credit one which ran 2512.03 seconds, the one linked above was a 21 credit WU that ran for 2516.56 seconds.

Actually i just saw the problem why they're running the same ;( While the astronomy_parameters file the assimilator was reading was changed, the sticky one in the download directory wasn't. I don't know if there's too much i can do about the WUs already generated with less credit, but the new ones should award the correct amount.

---