Quota and credit calculations. Not bad, not bad at all. |
![]() |
| log in |
Message boards : Number crunching : Quota and credit calculations. Not bad, not bad at all.
| Author | Message |
|---|---|
|
This new quota stuff, and new credit calculation stuff, looks pretty promising. | |
| ID: 1005177 · | |
I agree that it looks promising, but I can't help feeling that the GPU crunchers are going to get hit when they generate -12 errors (something that can't be avoided). ____________ | |
| ID: 1005179 · | |
It's going to be interesting to follow this over time. I followed it over time: Beta message 39533. Note that since that was posted, the number he first thought of has been doubled. So the intial spike should be even higher, and the long-term average should be lifted. But I expect the variability to remain. | |
| ID: 1005187 · | |
Even the autokill function should't penalize us. Because now SETI knows the application we use (CPU or GPU) and must be able not to send VLAR to GPU. So we have not to kill them. Who can agree? FF ____________ | |
| ID: 1005306 · | |
|
Nice idea, but it doesn't work like that. I have received over 100 VLARs for my GPU today. Also, I think I am right in saying that the stock CUDA application can handle VLARs, so as far as SAH is concerned, there is no issue. | |
| ID: 1005313 · | |
Over time it looks as if it is going to reward those that takes care of their WU's, and punishing those who deliberately abort them, or constantly turns in WU's that error out for one reason or another. I messed up a few days ago and lost a little over 100 WUs. They should start timing out over the next month and a half. The first of them on the 22nd of this month, the last of them on the 30th of July. By then everything should be running however they are trying to make it run so I guess these WUs will tell me what's what. My apologies to my wingmen by the way but right after I lost them I got a new bunch to replace them so I really can't detach to clear them. ____________ PROUD MEMBER OF Team Starfire World BOINC | |
| ID: 1005316 · | |
It's going to be interesting to follow this over time. Hmm, well lots of variability there I'd say. We'll see how this gets reveived among the participants here. I predict a s***storm :-) I'm not easily upset though, as long as the science we do is correct, I'm sitting down in the boat. ____________ /The grumpy old Swede. "I'm so old, that 98% of all trees in the forest, are younger than I am" | |
| ID: 1005340 · | |
|
Wonder when the storm from the members of other projects starts after they see some of us getting somewhere around 500 or 600 credits for one GPU WU? (I got one that paid 580 credits!} | |
| ID: 1005344 · | |
Wonder when the storm from the members of other projects starts after they see some of us getting somewhere around 500 or 600 credits for one GPU WU? (I got one that paid 580 credits!} Well, I've got some that normally would have give me over 100 and only gave 15-20. So I guess it average out somehow... ____________ /The grumpy old Swede. "I'm so old, that 98% of all trees in the forest, are younger than I am" | |
| ID: 1005347 · | |
|
I may have missed this in the plethora of opinion about the new scheduler setup, but my question is, now that the server is keeping track of CPU/GPU assignment what happens to work units that are reassigned using the rescheduler when they have been returned having been run by other than the platform to which they were originally assigned? Are they still valid? | |
| ID: 1005350 · | |
I may have missed this in the plethora of opinion about the new scheduler setup, but my question is, now that the server is keeping track of CPU/GPU assignment what happens to work units that are reassigned using the rescheduler when they have been returned having been run by other than the platform to which they were originally assigned? Are they still valid? Still valid, yes. The statistics of work done and how long it took are probably applied to the application to which they were originally assigned, though. Reassigning VLARs to the CPU may not be much problem, the run time may be similar to what they would have been on GPU. General rebalancing could have far more impact. Joe | |
| ID: 1005352 · | |
I may have missed this in the plethora of opinion about the new scheduler setup, but my question is, now that the server is keeping track of CPU/GPU assignment what happens to work units that are reassigned using the rescheduler when they have been returned having been run by other than the platform to which they were originally assigned? Are they still valid? Understood. Thanks Joe. | |
| ID: 1005356 · | |
|
Post moved elsewhere. | |
| ID: 1005357 · | |
|
So far seems to work as intended. Quota going up when returning valid work. Credit varying up and down, but may settle, or not :-) | |
| ID: 1005489 · | |
Message boards : Number crunching : Quota and credit calculations. Not bad, not bad at all.
| Copyright © 2013 University of California |