| log in |
Message boards : News : and a little payback
| Author | Message |
|---|---|
|
Since we had to wipe the database clean to get the server up and running, I know a lot of you lost a lot of credit on work you had done while the server has been down. So just as a thank you for everyone sticking with us while we've been dealing with these problems, and as a little payback for all the work lost; once we get the server up and running smoothly again we're going to have a temporary period of double credit (I'm thinking a day or two). Hopefully it will make up for a bit of the work that was lost. | |
| ID: 47270 | Rating: 0 | rate:
| |
|
Thank you for the thank you and also for all the work you guys have put in recently. | |
| ID: 47271 | Rating: 0 | rate:
| |
|
Great idea and thanks for all the hard work. | |
| ID: 47272 | Rating: 0 | rate:
| |
|
Great idea. | |
| ID: 47284 | Rating: 0 | rate:
| |
|
thanks | |
| ID: 47290 | Rating: 0 | rate:
| |
|
Thanks, but a thought though -- have it be two days from the point at which things are restored and running (relatively) smoothly. I suspect that the 'clock start' point for 2 days might be sometime on Monday... Since we had to wipe the database clean to get the server up and running, I know a lot of you lost a lot of credit on work you had done while the server has been down. So just as a thank you for everyone sticking with us while we've been dealing with these problems, and as a little payback for all the work lost; once we get the server up and running smoothly again we're going to have a temporary period of double credit (I'm thinking a day or two). Hopefully it will make up for a bit of the work that was lost. ____________ | |
| ID: 47326 | Rating: 0 | rate:
| |
Thanks, but a thought though -- have it be two days from the point at which things are restored and running (relatively) smoothly. I suspect that the 'clock start' point for 2 days might be sometime on Monday... I'll have an announcement for what days its going to be. I want to make sure things are running smoothly before we do it. ____________ | |
| ID: 47327 | Rating: 0 | rate:
| |
|
OK - that works, sort of a reward for paying attention <smile>.
____________ | |
| ID: 47405 | Rating: 0 | rate:
| |
Thanks, but a thought though -- have it be two days from the point at which things are restored and running (relatively) smoothly. I suspect that the 'clock start' point for 2 days might be sometime on Monday... Hmmm, that may be a good test if the server holds up ... and to motivate people to come back. Thanks for the thought, it counts for something, but - at least for me - it is not necessary. | |
| ID: 47622 | Rating: 0 | rate:
| |
|
Well, I will look forward to the extra credits, and will be very happy to say thank you. I think it's a decent gesture that will be well appreciated. | |
| ID: 47625 | Rating: 0 | rate:
| |
|
It is running smoothly I think doc Travis. | |
| ID: 47936 | Rating: 0 | rate:
| |
It is running smoothly I think doc Travis. let's wait for some other fixes. For example, I hope that they soon implement on the server side a message to hosts with too older drivers, that are trashing every workunit they receive, and to hosts with an incompatible (old) app (if not implemented yet). Then, let's wait for the final computation ported to gpu app, so that wu will be few seconds faster. Then I think it will be time to talk about double credits... At that time, project will be back to its original status! | |
| ID: 48065 | Rating: 0 | rate:
| |
I hope that they soon implement on the server side a message to hosts with too older drivers, that are trashing every workunit they receive, and to hosts with an incompatible (old) app (if not implemented yet). These should be blocked and erroring clients set to receive no work. The bad clients are causing problems, although not so obvious since WUs are cleared almost immediately after being discarded. I think it's the reason we're all seeing lower credits and is undoubtedly a major factor in keeping the database much larger than it should otherwise be. | |
| ID: 48067 | Rating: 0 | rate:
| |
|
How about a faster cpu app first too. | |
| ID: 48068 | Rating: 0 | rate:
| |
|
I agree, with the old 0.21SSE3 optimized app it took about 3 hours per unit, now with the default 0.50SSE2 it takes up to 12 hours... credits/day got cut by 75% too :) | |
| ID: 48069 | Rating: 0 | rate:
| |
How about a faster cpu app first too. I agree. This looks like the death knell for the cpu. The daily credits for cpu-tasks are really inadequate and barely worth the effort. | |
| ID: 48073 | Rating: 0 | rate:
| |
|
Are double credit days? | |
| ID: 48703 | Rating: 0 | rate:
| |
Are double credit days? BOINCstats is having server problems. The credit seems about the same as usual. You may notice it being a bit higher due to fewer validation errors. | |
| ID: 48705 | Rating: 0 | rate:
| |
|
BOINCstats is confusing me...ignore this post. | |
| ID: 48708 | Rating: 0 | rate:
| |
|
hello, | |
| ID: 48711 | Rating: 0 | rate:
| |
the double credit idea is ok and welcome but wouldnt you be better not announcing when it takes place Or just take a period of past days and run a script to double the user credit for that period. No extra server load at all :) | |
| ID: 48713 | Rating: 0 | rate:
| |
the double credit idea is ok and welcome but wouldnt you be better not announcing when it takes place... not all devout MW@H crunchers have the luxury of running MW@H 24/7 when they are equally as devoted to other projects. i cannot run MW@H and S@H on my GPU simultaneously. as such, i have to suspend MW@H while crunching S@H and vice versa. if i suspend MW@H to catch up on some S@H work, and no announcement is made about the double credit period, i could get screwed along with lots of other "ordinary" crunchers. in short, this solution leaves quite a bit to be desired. Or just take a period of past days and run a script to double the user credit for that period. No extra server load at all :) i don't know if its a simpler solution with respect to coding, but it sure seems like a much better solution. ____________ | |
| ID: 48714 | Rating: 0 | rate:
| |
|
ok, it was an error of the boinc Server, now it's corrected, and the extra credit is away :-(. | |
| ID: 48715 | Rating: 0 | rate:
| |
Mayby some more Wu's in the cache (24/GPU would be nice). Seconded, +1! | |
| ID: 48717 | Rating: 0 | rate:
| |
|
Seconded +2! Or just take a period of past days and run a script to double the user credit for that period. No extra server load at all :) nice idea too Ian ____________ ....Please Join team Scotland HERE | |
| ID: 48720 | Rating: 0 | rate:
| |
Or just take a period of past days and run a script to double the user credit for that period. No extra server load at all :) This is a very good idea. No one knows when it happend and the to MW devoted crunchers get the credits. However I must admit I don't crunch for credits, only the science I find usefull and interesting. And for MW only during cheap power rate hours. ____________ Greetings from, TJ | |
| ID: 48790 | Rating: 0 | rate:
| |
|
It should be for existing users only. Since new users would not have had an 'inconvience'. | |
| ID: 48799 | Rating: 0 | rate:
| |
It should be for existing users only. Since new users would not have had an 'inconvience'. I think this will be too exhausting and ther wil be no advertising effect for new crunchers. | |
| ID: 48805 | Rating: 0 | rate:
| |
It should be for existing users only. Since new users would not have had an 'inconvience'. The last few times word got round and crashed the server. ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 48806 | Rating: 0 | rate:
| |
It should be for existing users only. Since new users would not have had an 'inconvience'. I agree. Should be done quietly and surreptitiously and all the crunchers will get a happy surprise. | |
| ID: 48808 | Rating: 0 | rate:
| |
It should be for existing users only. Since new users would not have had an 'inconvenience'. I could work with that. ____________ | |
| ID: 48814 | Rating: 0 | rate:
| |
|
and the sooner the better... | |
| ID: 48817 | Rating: 0 | rate:
| |
and the sooner the better... I'd still like a cpu app first. ____________ Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. | |
| ID: 48822 | Rating: 0 | rate:
| |
|
We have taken note of all the suggestions. We really need to get the bug of workunits getting canceled early fixed first. After that it'll be a go So it is on it's way. Please refrain from asking when it will occur--I assure you it will occur when we have resolved the above issue. Thank you for your patience. ____________ | |
| ID: 48823 | Rating: 0 | rate:
| |
|
Thank for the update! | |
| ID: 48829 | Rating: 0 | rate:
| |
|
What about the remaining last 12 hours of these? ^^ :) | |
| ID: 51713 | Rating: 0 | rate:
| |
Message boards :
News :
and a little payback