I would also look into BOINC, since it can help making users aware of the project in addition to actually being such a framework.
http://boinc.berkeley.edu/intro.php
Type: Posts; User: larsivi
I would also look into BOINC, since it can help making users aware of the project in addition to actually being such a framework.
http://boinc.berkeley.edu/intro.php
Keroberts1 wrote:
I wasn't talking about the main .dat file, but to continue the 300K-3M sieving a little while longer. Just wondering whether it's worth it, really.
I saw that quite a lot of new supersecret tests have been added. Won't it be of interest to run n < 1M sieving until no further tests (or at least just a few tests left) for n < 1M has been left...
I think you should read the forum more thouroughly before asking questions :)
Check out
http://www.free-dc.org/forum/showthread.php?s=&threadid=4860
Washuu wrote:
I think mklasson mentions a paper about one or more such algorithms in the 'sieve client' thread. The thread is long, but probably worth reading if you're really interested.
The Nano@Home project has considered BOINC. A fairly thourough discussion can be found at the
Nano@Home forums. Many good points, pro on con.
I've had 417 kps on the low range with an Athlon 1.33 GHz
It's working but it is veeeeery slow. It took one minute to get a response from the website, and mklassons sobistrator is still working (after 5 minutes) with submitting 10 factors.
mklasson:
They came back with the refresh, but with the new version they didn't disappear at all.
Tjänare!
sobistrator bug?
I had a few new factors which I tried to submit. Since seventeenorbust.com was down, the submit failed and I got a message about submitting the factors manually. Fair enough, but...
No, I can't access it either.
Yes, of course. Sorry. Windows Update is a service that is available in (at least) WinXP. It seems to continiously search MS' pages for updates to relevant software, mostly security updates and such....
Speed 'tip': proth_sieve went from 400kp/s to 320kp/s on my AMD 1.33GHz when I enabled Windows update. It went back to 400 when I disabled it again.
btw, I'm sieving low range only.
mklasson:
Some numbers low sieving range, around 11T:
proth_sieve_windows_cmov, v0.33 reported 259k p/s as maximum
SoBSieve 1.28 reported 333k p/s as maximum
The machine is an 1.33 GHz...
I don't, but I DID test it ouf of curiosity. I was then assigned the k=22699/n=3667222 test, which is the lowest unfinished test on the stats page.
Don't forget the cool accounts you can use if you don't care too much about stats:
1. secret - doublechecks PRP-tests, especially those predating SOB (some numbers at...
Have you tried the smp-client? It isn't listed on the download-page, but can be found at:
http://www-personal.engin.umich.edu/~lhelm/sb-smp.exe
I guess it's windows only, but it might reveal...
Well, there are no more supersecrets (the 400k limit has been reached). Secret tests are now assigned instead.
As far as I can see, it's only the 67607 range that has a correct "max n tested" value at the moment. The others have had values above 4 million several tests before I got my first test above 4...
Frodo42 wrote:
I would suppose that the reason for the higher number of completed tests lately would be due to Ars Technicas SoB gauntlet from 9th of June to 9th of July.
larsivi
I am not only talking about US' military power (or Germany's for that sake), but about the decrease in civil rights for the average US citizen. When a company is allowed to staple us citizen's as...
It's opinions of the sort that jimmars shows that scares me most. When such a view is legislated systematically, it can only lead to more violence and/or fear.
The stuff going on in the US now is...
heh,
just noticed the tick off box in the config dialog where I could choose whether SoB should start on windows bootup or not...
Lars Ivar
Yes, thank you. Just what I needed (the startup program)
Lars Ivar
Hi!
As many probably knows, XP makes it possible for two or more users being logged on at the same time. SoB doesn't separate the installing user from the rest, resulting in the client starting up...