Well, the constant rise of n values lately for secondpass has definitely been increasing our production potential… Looks like we’ll probably take 28th spot tomorrow evening
And there were a few of us I think that were “lucky” enough to get a first-pass n before they repopulated the error-fix queue again.
One of my machines is chewing away at a ~9M n value from first-pass that still has ~900 blocks left at 80% complete! - but the rate is phenominal compared to the 4M values that we were testing a while ago.
Unfortunately, many of my slower machines will be staying on secondpass using the usernameQQQsecondpass method - as it would take months for some of my older machines to chew through a >9M n value - so there’s no point in forcing them to do so.
If SoB comes out with the 3.x client, it should support seiving, etc. with all work attributing to the user/team’s points. I can’t wait for this, as I will gladly donate my older machines to seiving time where they would be most effective.
Well, the constant rise of n values lately for secondpass has definitely been increasing our production potential...
My numbers don’t add up. SOB lists my total about 2K cEMs/sec, yet I should have that on my HT alone. Hmm… I guess I’ll try a reboot.
Oops, i edited your post instead of quoting it - hopefully it’s fixed.
In any case, I suspect you mean 2M cEMs/sec - and yes - i get about that between the 2 tests running on my P4 3ghz HT machine running two 5M n values.
If you saw a decrease, it’s most likely due to the lower n values that were dumped into the error-fix queue recently - once you finished your last secondpass test, it probably snagged a lower errorfix n value that decreased your cEMs/sec again… not to worry…
Hopefully they’ll get that 3.x client AND the new points system going soon - that would make everyone happy i think
Oops, i edited your post instead of quoting it :P - hopefully it's fixed.
Note - I edited my post probably while you were replying.
umccullough wrote:
If you saw a decrease, it's most likely due to the lower n values that were dumped into the error-fix queue recently - once you finished your last secondpass test, it probably snagged a lower errorfix n value that decreased your cEMs/sec again... not to worry...
Problem was, it wasn’t showing that way on my clients. They both had 1000K on them. I’ve reset and the numbers are more in line. It also seems to have picked up some speed from the actual 1.3M rate.
Note - I edited my post probably while you were replying.
No, I actually clicked the edit button instead of quote and added my reply to your post - then I went back and edited it again to remove it - first time i’ve made that mistake.
Katisu wrote:
umccullough wrote:
If you saw a decrease, it's most likely due to the lower n values that were dumped into the error-fix queue recently - once you finished your last secondpass test, it probably snagged a lower errorfix n value that decreased your cEMs/sec again... not to worry...
Problem was, it wasn’t showing that way on my clients. They both had 1000K on them. I’ve reset and the numbers are more in line. It also seems to have picked up some speed from the actual 1.3M rate.
I think it does some weird crap where it shows the average cEMs/sec over the entire period it’s been running on the client screen - i’ve noticed that it tends to show some pretty useless information sometimes also.
I almost did this morning - but I figured I’d give him the rest of the day
I gave up on him and stole his thunder.
I guess he’s too busy fighting the EU on “privacy”.
Personally, the US government does actually have more important things than to spy on Americans, such as myself. There are plenty wasteful spending projects, finger pointing, campaigning, posturing, progress-stalling distractions, and back pocket deals that demand more of their attention.
- hopefully it’s fixed.