I also believe double checks are worth it. Basically, if we have a 5% error rate, then it's even faster to find a prime if we can complete a double check in 1/20th the time of an initial check.
A...
Type: Posts; User: shifted
I also believe double checks are worth it. Basically, if we have a 5% error rate, then it's even faster to find a prime if we can complete a double check in 1/20th the time of an initial check.
A...
Should be mgoetz [at] primegrid [dot] com :)
I don't keep all my logs, but I'll see what I have. I was one of the top contributors.
There might be a new update soon when mprime is updated to best support Haswell processors. Who knows. I'm still crunching primes.
1.0.2 Will crash on Mandrake 9.1 ( Kernels 2.4.19 to 2.4.21, glibc 2.3.1 ) if a hostname is specified instead of an IP. Immediate segfault on startup.
1.0.2 Runs fine on Debian Woody (3.0 stable)...
Hmm... the sb client does leave a pile of TCP ports in the CLOSE_WAIT state... maybe that is what is causing the crashing. It would make sense that it runs out of resources and dies.
Hmm... the sb client does leave a pile of TCP ports in the CLOSE_WAIT state... maybe that is what is causing the crashing. It would make sense that it runs out of resources and dies.
Switch the host name in the sclient.conf file to the IP addy 216.163.34.105. That should fix your 1.0.2 problems with newer linux distros (mandrake 9.0/9.1 also).
If you overclocked your box, try clocking it to its rated speed.
I have seen the same thing happen with 1.02... usually after several days.
In sbclient.conf change the hostname to its IP address, which is 216.163.34.105. I just figured that out.
Someone from here encouraged me to get back involved with sb... so here I am.
This doesn't matter as the program spends almost all the execution time in the assembler core.
I was working on a port, but with the recent rate of prime discoveries (about one a week!), I no longer consider it a wise investment of time (at the moment).
The current SoB client has an x86...
I want one! lol
Well, dection would be good, so we can prepare our defences... making contact, on the other hand...
Very good point. I'd stick with the whois stuff as it's reasonably accurate now and already implemented.
An easy overclock to try is changing the CAS setting in the bios from 3 to 2. This reduces access latency a little bit. Most memory will take it, but it may be unstable with cheap ram (expensive...
Take off every 'zig'
For great justice!
That's the same reason why we have multiple levels of government?in case one level fails to screw up, the next will! :D
NT = Nice Try
Yep, that manual update fixed my stats also. Hmm... Good luck on debugging it.
Also, check out the stats for team shifted. It consists entirely of me, and it's exhibiting the exact same anomalies...
Yep!
Just remember 6 x 9 = 42 in base thirteen! I think we should all switch to base thirteen in memory of Adams.
No, i'm not 100. I was born 10100 years ago :P
LOL...
/me was thinking the same think
/me was hoping they'd all go away so me would be back in the top ten
My windows machine is running on an MSI 6330 Lite board, based on VIA KT133. It's a low-end, DDR266 board running an Athlon TBird at 1400, but those new Via drivers did boost performance by about...