Reply With Quotemklasson:
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 Athlon
it would be nice to see a version as user friendly as the old one and perhaps wit hthe same lay ourt just so it would be easier to use/ monitor.
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 Athlon
larsivi:
I see about a 15% speedup on my system when sieving just 300K-3M instead of 300K-20M, so if that's what you're getting as well then all is normal.
Proth_sieve is not all that affected by the size of the n range. You should probably just stick with sobsieve 1.28 for the low sieving range.
Thanks for the numbers though,
Mikael
Hm, strange...
The last 60+ factors I got (using SoBsieve) are quite evenly distributed across all n's - except the 4M section.
How about you?
Alas, I haven't gotten a high-scorer for close to 200 factors now... Had one this morning that was 30k below the prp bound. Ack!Hm, strange...
The last 60+ factors I got (using SoBsieve) are quite evenly distributed across all n's - except the 4M section.
How about you?
Woohoo, got one!
37207258041013 | 24737*2^4401127+1
Was this finding pure coincidence?*cough* conspiration *cough*
Too bad it's less than 40T.
Ah right, I remember...
More benchmarking:
-= Tualatin@10x142 W2K SP4 =-
*** "normal" ***
proth_sieve 0.31
pmin : 60000000000000
pmax : 60000010000000
# Tested p : 314507
# Tested k : 3774084
# Whacked k : 2975683
# Whacked p : 77661
Total time: 44325 ms
225k p/s.
proth_sieve 0.32
pmin : 60000000000000
pmax : 60000010000000
# Tested p : 314507
# Tested k : 3774084
# Whacked k : 2975683
# Whacked p : 77661
Total time: 44585 ms
224kp/s.
proth_sieve 0.33
pmin : 60000000000000
pmax : 60000010000000
# Tested p : 314507
# Tested k : 3774084
# Whacked k : 2975683
# Whacked p : 77661
Total time: 44143 ms
226kp/s.
*** CMOV ***
proth_sieve_cmov 0.31
pmin : 60000000000000
pmax : 60000010000000
# Tested p : 314507
# Tested k : 3774084
# Whacked k : 2975683
# Whacked p : 77661
Total time: 42933 ms
232k p/s.
proth_sieve_cmov 0.32
pmin : 60000000000000
pmax : 60000010000000
# Tested p : 314507
# Tested k : 3774084
# Whacked k : 2975683
# Whacked p : 77661
Total time: 42712 ms
234kp/s.
proth_sieve_cmov 0.33
pmin : 60000000000000
pmax : 60000010000000
# Tested p : 314507
# Tested k : 3774084
# Whacked k : 2975683
# Whacked p : 77661
Total time: 41860 ms
238kp/s.
SoBSieveConsole 1.34: 236 kp/s
At 52336 G
- proth_sieve_cmov 0.33: 244 kp/s
- SoBSieveConsole 1.34: 236 kp/s
Troodon:
Let me provide a gentle reminder that you'll get more correct (and higher, probably around that 244k figure for cmov) rates if you benchmark ranges that are multiples of 8 million wide.
Yes, I know, but I wanted to test it in an adverse scenario. Thanks for your great work!
Another benchmark:
Athlon XP 1700+ (Palomino), WinXP SP1, 52424 G
SoBSieveConsole 1.34 - 274 kp/s
proth_sieve CMOV 0.33 - 256 kp/s
To quote myself:
"Feeling lazy? Want to make the chore of managing all your factors a little more automated? Try the new sobistrator v1.10! [windows only]"
This program lets you keep track of multiple machines' sieving efforts and collect new factors from them with a single click. It can optionally launch the submit page automatically and reduce your effort to a paste operation.
I like it.
Have a go at http://n137.ryd.student.liu.se/sob.php if you want to try it.
I originally made this strictly for myself, but I figure someone else might enjoy it as well.
Regards,
Mikael
I've been running the sobistrator 1.10 for a few days now, and I can highly recommend it!
...it's to bad I don't have more than one computer...
Shooting myself in the foot stats-wise, I present you with proth_sieve v0.34.
It's about 10% faster than v0.33, with the linux version something like a whopping 20% faster.
This one finds far less duplicates, because it forces all found factors' n to lie in the same residue class modulo "t" as the remaining unfactored n do. I previously hadn't implemented that idea in the new discrete log algorithm. Additional linux speedup is due to new gcc (3.3) and removal of some redundant variable copying.
"Outside range" factors are now able to go a lot higher, but are more rare. They're pretty useless, but free.
Factors with n < lower limit are also written to factrange.txt now. They used to go to factexcl.txt.
Head on over to http://n137.ryd.student.liu.se/sob.php
Cheers,
Mikael
At the risk of talking to myself, here's a new version again. This one's about 16% faster than v0.34.
I get roughly 420kp/s on my 2030MHz athlon now.
Are you using this yet?
http://n137.ryd.student.liu.se/sob.php
EDIT: Oh, I forgot. A new feature in this version is that you can write new ranges in a text file called nextrange.txt and have proth_sieve automatically start working on the next one after it's done with the current. Ranges are given on two lines, just like in sobstatus.dat.
pmin=12345000000000
pmax=12346000000000
for example.
*** SoBSievers BEWARE! *** SoBStatus.dat is erased when the new range is started, so if you've been using SoBSieve and have factors in SoBStatus.dat you'd better copy them before creating a nextrange.txt.
Regards,
Mikael
Last edited by mklasson; 08-29-2003 at 07:39 AM.
I went from 160k to 210k in a matter of days using proth_sieve 0.33-0.35.
Last time I used sobsieve it gave me 140k.
You do the maths...
Oh, FYI I'm using a P4 2.4GHz system.
Wouldn't it be better to do P-1 factoring then? I mean, my 1 GHz P3-m even does ~ 205kp/sec.Oh, FYI I'm using a P4 2.4GHz system.
Whereas it would completely suck vs. your P4 when doing factoring...
btw. the sieving rate dramatically increased from ~ 160kp/sec when changing from SoBSieve to Proth_Sieve.
Really nice work, mklasson!
Oh, and nice country you live in - I was there on camping tour some weeks ago.
Last edited by Mystwalker; 08-29-2003 at 08:48 AM.
Don't you think the P4 still does more good sieving at that rate than P-1:ing though?Originally posted by Mystwalker
Wouldn't it be better to do P-1 factoring then? I mean, my 1 GHz P3-m even does ~ 205kp/sec.
Whereas it would completely suck vs. your P4 when doing factoring...
Thank you! Yeah, too bad it's so much easier to appreciate a country when you don't live in it every day.btw. the sieving rate dramatically increased from ~ 160kp/sec when changing from SoBSieve to Proth_Sieve.
Really nice work, mklasson!
Oh, and nice country you live in - I was there on camping tour some weeks ago.
Mikael
That's true, but I find that sieving is more efficient still. I tried P-1 factoring a couple of months ago but found only one factor in a range of 5500 candidates. So...I'd rather do some PRP tests instead of P-1. But It's boring...:sleepy:...at least you find something when sieving..Originally posted by Mystwalker
Wouldn't it be better to do P-1 factoring then? I mean, my 1 GHz P3-m even does ~ 205kp/sec.
Whereas it would completely suck vs. your P4 when doing factoring...
Proth_sieve 0.35 now is faster than sobsieve 1.34 on my computer (XP 1600+)
proth_sieve 0.35 295kp/s
sobsieve 1.34 260kp/s
Good job!
I'm not sure with that. Sieving gives us a lot more factors, but most of them are not useful right now or in the next weeks. So one could do factoring now, as there is a lot of power urgently needed (big ranges can't be trial factored before PRP catches up), and later switch over to sieving again.Originally posted by Xrillo
That's true, but I find that sieving is more efficient still.
I don't know about the best factoring <--> sieving ratio, but I think it's not bad to let the machines do what they are most useful to do - P3, AMD sieving; P4 PRP or factoring.
But it's just instinct, can't prove anything.
I guess winter is not that joyful sometimes - how long are day times then?Originally posted by mklasson
Thank you! Yeah, too bad it's so much easier to appreciate a country when you don't live in it every day.
Mikael
btw. doing even close to 210kp/sec (sometimes even reaching it)
Best of all will be when p-1 is integrated into the prp client.I'm not sure with that. Sieving gives us a lot more factors, but most of them are not useful right now or in the next weeks. So one could do factoring now, as there is a lot of power urgently needed (big ranges can't be trial factored before PRP catches up), and later switch over to sieving again.
At its worst, the sun sets around 15 in the afternoon or so. That's not the worst part though... That'd be the horrible screams of the polar bears clawing at your back! It's enough to drive a man insane...I guess winter is not that joyful sometimes - how long are day times then?
Theoretically yes, but Louie raised a good point there: It is expectable from the user that he grants the client to use 256 or 512 MB RAM? I think a lot of ppl won't (be able to) do this.Originally posted by mklasson
Best of all will be when p-1 is integrated into the prp client.
15 o'clock? Well, that's a lot better than I thought. A "dawn at 11:45, dusk at 12:15" was what I expected.
At its worst, the sun sets around 15 in the afternoon or so. That's not the worst part though... That'd be the horrible screams of the polar bears clawing at your back! It's enough to drive a man insane...
Even here, it gets dark around 16:00 for some days...
But we have less polar bears
> Theoretically yes, but Louie raised a good point there: It is expectable from the user that he grants the client to use 256 or 512 MB RAM? I think a lot of ppl won't (be able to) do this.
Considering that it's just for an hour twice a week, _I_ think that's pretty ok. Besides, they don't have to allot that much memory -- it's just speedier if they do.
Mikael,
Congratulations, a truly astonishing achievement. You were straight out the box with a client that's faster than anything around for Linux, and anything pre-CMOV. Within two weeks you have overtaken Paul's clients on every platform and OS.
This is an astonishing accomplishment. Paul and Phil have been at this for years, don't be surprised if you have other projects with sieving needs knocking on your door!
I've just this evening started to use v0.35. On my AMD XP2100 I get 356kp/s vs 316kp/s with sobsieveconsole 1.34. I've been using my own automation s/w for a while, but I'll now be taking a look at sobistrator.
Keep up the great work.
Mike.
P.S. You really should talk to Paul. If he has some super efficient bits of assembler that he's willing to share maybe you could get this thing much faster still.
the proth sieve client is giving me a rate of 304 while i had 316 with sobsieve does that mean the sobsieve is faster or is the rate not registering right one one of them
For me proth_sieve 0.33 (Linux version) works fine, but 0.34 and 0.35 segfault when they start sieving (I'm working with Mandrake Linux, I don't know exactly which version).
What hardware platform and OS are you using? And which versions of the clients are you uisng?the proth sieve client is giving me a rate of 304 while i had 316 with sobsieve does that mean the sobsieve is faster or is the rate not registering right one one of them
MikeH,
thanks for the kind comments!
chvo,
it isn't simply a case of accidentally running the cmov-version on old hardware? Anyway, what processor are you running it on, and which program version are you using -- cmov/regular, static/nonstatic?
I'm using proth_sieve cmov static on a P4 (the static cmov 0.33 version worked fine, however now it segfaults when it starts sieving!?)
I wasw using 0.34 with cmov on an AMD athalon 2000+ but since upgrading to 0.35 i have had a surprising speed up so I'm good now
Is anyone else sieving (or trying to) with a P4 under linux, and if so do you have the same problems as chvo? I'm having a tough time finding the cause of this as I don't have any P4s myself and it works just fine on my machines.
Mikael
I've started using 0.35 yesterday and I have a question. But, fisrt things first: Congratulations Mikael.
I'm using the client on 46.x T, and over roughly 60G of sieve range, the client found the following number of factors:
Unique: 23
Duplicate: 341
Out of range: 82 (only 41 of which is accepted by the sieve submission page).
The number of unique factors seemed fine to me, but the number of out of range factors, and especially the number of duplicates are .....
Are those figures normal? Any comments?
B.T.W.:
Hardware: AMD Athlon XP 2400+ (2.0GHz)
System: Microsoft XP
Range: 3M-20M
Nuri,
thanks!
The upper "deranged" factors, the ones above the upper limit, can pop up when p-1 is highly composite, but as for what the count should be... I'm sure 41 is just fine.
I have a feature request:
Could you add an option to use a SoB.dat file in a different folder?
That would it make possible to use one dat file for several computers that work on the same NFS...
btw.: Linux version is only 3-4% slower than Windows client on a P3-800.
Good news everyone.
Paul and I have teamed up and are collaborating on proth_sieve now. The fruits of our labors is a new proth_sieve v0.36 that scores a very pleasant 530kp/s on my Athlon 2030MHz. That's up about 25% from v0.35. Also new in this release is a little SSE2 support. Not a major boost, but a fine 10% or so on P4 machines.
Thanks to Christian Nilsson (Xrillo) for helping out with that part. The SSE2 enhanced flavor only exists for windows, because I have no chance whatsoever of testing a linux SSE2 version. Feel free to contact me if you want to try a linux version.
New features include the support for alternative sob.dat files that Mystwalker wanted (-s argument). The rate is also output to sobstatus.dat now, which brings me nicely to the second program...
I've put up a new sobistrator v1.13 if you're into that kind of thing. New in this version is rate display, ETA, managing next ranges (nextrange.txt), and factor submission. Click submit when you've got new factors waiting and sobistrator will send them to the seventeenorbust site for you. Don't worry, you can configure it to log in with your name and password so you'll get full credit for the factors.
As usual, the goodies are at http://n137.ryd.student.liu.se/sob.php
EDIT: Of course I forgot to mention that there's an older v0.354 SSE2 included in the SSE2 package. That one seems to be a couple of percent faster than v0.36 SSE2 for some reason. Use whichever you want.
Regards,
Mikael
Got "only" 15-20% performance increase, but I think that's still worth a big cheer!
Just updated my systems, running fine. The -s parameter helped me save a lot of space. I don't know my quota, but I think it's good not to reach it.
Just thought about it... When it's possible to set the output file names via parameters (or maybe a parameter so that the files get an infix according to the range), then one should be able to run one copy multiple times in parallel, right?
I could hook up a lot of machines that way without the need to create further copies...
The new client and especially the sobistrator motivated me to work on my SoBSieveServer again. Hope I get enough time at the weekend.
Ah, the sweet smell of competition.
Note: That server is no rival for the sobistrator - it could rather further enhance it...
Last edited by Mystwalker; 09-04-2003 at 07:20 PM.
I've having trouble downloading the programs. Is the site down? Maybe not it could just be a problem wiht the connection on my end.
Ok the problem as on my end but i have a new one. The sobinstrator says when i try to open it this application failed to start because MFC71.DLL was not found. Re-installing the application may fix this problem. Obviously that didn't help. Anyone know what i need to do?
Posting Permissions
