While this bug still exists, would it be a good idea to not send out more work units? I know that some folks would complain, but it seems to me that it would lessen the chance of getting bad results.
Probably would've been a good idea early on, but perhaps not now. I would guess it would depend now on being able to correctly identify such results and the incidence rate of such a result. If the failure rates are low and the results can be identified fairly easily, then they could just be reprocessed during the remainder of the S5R2 run or at the very end of the run...
Coming up with those answers is likely the highest priority for the scientists now...
This bug was there and needed to be fixed, but it turned out that it is not responsible for (all of) the platform discrepancies. We're still looking into that.
Will you be releasing a new app with that bug fixed, or holding off until you can try and localize the remaining issues?
A new Beta App for MS Windows will be released in the next few days (hopefully tomorrow), it will at least reduce the client errors that arise from this bug. A release of a complete series of Apps for all platforms has be postponed until we know a bit more about the problem.
I am noticing a significant performance improvement on my AMD x2 4200 system using the new beta app. The speed improvement seems to be on the order of 25%. Whatever was done, it is much appreciated.
Just out of curiousity does this also speed up and adjust the cobblestones credit? Or will the next beta version? I finally had to stop processing for E@H about a month ago while I was waiting for these things to get fixed. 30+ hours for 300+ credits and "MAYBE" someone else in my lifetime be able to fill the quorum was just too much for me. I did my best to try and tough it out, but it seemed it get worse instead of better. I got my last credit less than a week ago .. that one took almost 6 weeks!
In the meantime I'm running CPDN 100% instead of the 50/50 I had before.
It dos`nt adjust the credit but I`ve seem my crunch time come down from just over 36hrs to just over 28hrs for a 341 credit wu from the same data pack. AMD XP2400+.
RE: While this bug still
)
Probably would've been a good idea early on, but perhaps not now. I would guess it would depend now on being able to correctly identify such results and the incidence rate of such a result. If the failure rates are low and the results can be identified fairly easily, then they could just be reprocessed during the remainder of the S5R2 run or at the very end of the run...
Coming up with those answers is likely the highest priority for the scientists now...
Brian
This bug was there and needed
)
This bug was there and needed to be fixed, but it turned out that it is not responsible for (all of) the platform discrepancies. We're still looking into that.
BM
BM
Will you be releasing a new
)
Will you be releasing a new app with that bug fixed, or holding off until you can try and localize the remaining issues?
RE: Will you be releasing a
)
A new Beta App for MS Windows will be released in the next few days (hopefully tomorrow), it will at least reduce the client errors that arise from this bug. A release of a complete series of Apps for all platforms has be postponed until we know a bit more about the problem.
BM
BM
I am noticing a significant
)
I am noticing a significant performance improvement on my AMD x2 4200 system using the new beta app. The speed improvement seems to be on the order of 25%. Whatever was done, it is much appreciated.
Just out of curiousity does
)
Just out of curiousity does this also speed up and adjust the cobblestones credit? Or will the next beta version? I finally had to stop processing for E@H about a month ago while I was waiting for these things to get fixed. 30+ hours for 300+ credits and "MAYBE" someone else in my lifetime be able to fill the quorum was just too much for me. I did my best to try and tough it out, but it seemed it get worse instead of better. I got my last credit less than a week ago .. that one took almost 6 weeks!
In the meantime I'm running CPDN 100% instead of the 50/50 I had before.
Hoping to be back soon....
It dos`nt adjust the credit
)
It dos`nt adjust the credit but I`ve seem my crunch time come down from just over 36hrs to just over 28hrs for a 341 credit wu from the same data pack. AMD XP2400+.
See here. BM
)
See here.
BM
BM