What the heck has happen to workunit credits? |
![]() |
| log in |
Message boards : Number crunching : What the heck has happen to workunit credits?
1 · 2 · Next
| Author | Message |
|---|---|
|
Suddenly I'm getting squat credits (4-13) for workunits that use to give me 80 or more (based on how long it takes to crunch). I don't check in here as often as I should but did something recently (last 3 months) change in how it gets calculated? | |
| ID: 1239427 · | |
|
A year, or was it two, they changed things with CreditNew. Which has its ups and down. There are a few topics on the subject. | |
| ID: 1239429 · | |
In both of these cases the workunit was crunched by the same wingman using "SETI@home Enhanced Anonymous platform (NVIDIA GPU)" on their GTX 590. Morten Ross is running an extremely recent 'Multibeam x41x Preview, Cuda 4.20' test application on all six GTX 590 devices in his Longhorn server. I think this must be a hand-picked test unit - hopefully it is being closely monitored (not least, for side-effects of the current server bug). | |
| ID: 1239431 · | |
In both of these cases the workunit was crunched by the same wingman using "SETI@home Enhanced Anonymous platform (NVIDIA GPU)" on their GTX 590. Agreed. Just checked another cuda alpha host with same result. 10-30% causes in low credit. ____________ | |
| ID: 1239434 · | |
In both of these cases the workunit was crunched by the same wingman using "SETI@home Enhanced Anonymous platform (NVIDIA GPU)" on their GTX 590. Well, I'm running the same application myself (which is how I know how new it is), and I don't see any sign of lowered credits on my hosts. I don't think it's an application issue, but I wondered if the overall performance of BOINC on a host with that many devices was being monitored. | |
| ID: 1239443 · | |
In both of these cases the workunit was crunched by the same wingman using "SETI@home Enhanced Anonymous platform (NVIDIA GPU)" on their GTX 590. You have some as well. http://setiathome.berkeley.edu/result.php?resultid=2461040880 ____________ | |
| ID: 1239500 · | |
In both of these cases the workunit was crunched by the same wingman using "SETI@home Enhanced Anonymous platform (NVIDIA GPU)" on their GTX 590. Interestingly, my wingmate (the valid one) on that one was another server OS. That's one of the major weaknesses of 'CreditNew' - we can no longer see which member of the quorum pair is making the low claim, which makes it much harder to analyse whether a host has a consistent problem. But thanks - I'll keep an eye on it. | |
| ID: 1239503 · | |
|
Look at this example no Windows server involved. | |
| ID: 1239507 · | |
|
I think the servers messed up. | |
| ID: 1239515 · | |
I think the servers messed up. Good spot. At least is shows that x41x isn't the only application demonstrating these characteristics. Question is, how widespread is this issue...... ____________ | |
| ID: 1239519 · | |
I think the servers messed up. At least all wingmen were cuda. Not one ATI result messed up. ____________ | |
| ID: 1239525 · | |
I think the servers messed up. That particular case is exactly the one I wrote up on Monday in Host falling back to CPU processing... (the thread title is from an earlier mis-diagnosis). It comes - or came then - when you report more than 64 tasks at once, and request new work at the same time. Maybe no ATI cards could complete 64 tasks during the outage? :P | |
| ID: 1239568 · | |
|
I'd like ot know why I got over 2000WU's after the previous outage. Suddenly using BOINC 7.0.28 gives me an enormous cache. | |
| ID: 1239595 · | |
|
I used to get around 90 for each WU now with my WU with either Fermi or Cuda I only get 30 so I have lost two thirds of my credits I have only noticed this since the outage | |
| ID: 1239600 · | |
I think the servers messed up. Now that's a weird one. Run time was 323.00 Seconds, but CPU time was 6,747.00 seconds, still it was finished and uploaded in just over 5 minutes. Sent from SETI 1 Jun 2012 | 1:10:18 UTC Time reported: 1 Jun 2012 | 1:15:41 UTC It's definitely something very strange going on there. Edit: Just noticed Richard's explanation for this one. Consider this entire message of mine, as a waste of bandwidth. LOL ____________ /The grumpy old Swede. "I'm so old, that 98% of all trees in the forest, are younger than I am" | |
| ID: 1239612 · | |
I used to get around 90 for each WU now with my WU with either Fermi or Cuda I only get 30 so I have lost two thirds of my credits I have only noticed this since the outage I think we are definitely in the realm of unintended consequences..... ____________ | |
| ID: 1239616 · | |
I think the servers messed up. I reported 587 at once yesterday without a problem. scratching head. ____________ | |
| ID: 1239680 · | |
I reported 587 at once yesterday without a problem. I was reporting hundreds of WUs at a time yesterday, but only 64 would actually be reported with each contact with the Scheduler. And luckily at the time there were hundreds of WUs still uploading while i was hammering the update button so i didn't request new work while trying to report. ____________ Grant Darwin NT. | |
| ID: 1239694 · | |
I reported 587 at once yesterday without a problem. Check - count, even - the number of 28-May-2012 10:11:47 [SETI@home] [sched_op] handle_scheduler_reply(): got ack for task 16dc10ac.2114.14009.12.10.195_0 you get in reply to your 587. You run <sched_op_debug>, I'm sure? It's the only way to keep an eye on what's happening round here. | |
| ID: 1239699 · | |
|
Sure i do. | |
| ID: 1239701 · | |
Message boards : Number crunching : What the heck has happen to workunit credits?
| Copyright © 2013 University of California |