Search:

scrap, d.net's FAQ is very oudated! Riva 128 appears as example, and it's a chip from 1998. The current chips are very different - AFAIK they're programable (but not as flexible as a CPU) and have FP...

No, of course :) .

I have a Celeron Tualatin with Windows 2000 and some time ago I have discovered this "trick":
1. The computer boots.
2. I start SB. It gets X cEM/s. I close it.
3. I start proth_sieve and let it...

And what is keeping you from coming back? If you really want to help this project (and have some free RAM), please do some P-1 factoring. If you're more interested in stats, sieving and P-1 have...

While waiting the server to be back, you could help with sieve and/or P-1 factoring. It's a great chanche to boost P-1 factoring :) .

Some ideas:
- When you find a factor by sieving, you save the need for a PRP test AND for a P-1 test.
- With sieving, as we're getting deeper, the density of factors is decreasing. That means more...

It's highly recommendable to P-1 factor an assigned k/n pair before testing it! But before that, check in the coordination thread if it hasn't been factored before ;) .

640 Mb

More benchmarks:
sbfactor 4847 5000007 100 150 [mem]

***********
With mem=32
***********
Memory used (kB)=36700 (1.1); 36704 (1.1 dev)
Memory allocated (kB)=37816 (1.1); 37856 (1.1 dev)...

Another benchmark:
Athlon XP 1700+ (Palomino), WinXP SP1, 52424 G
SoBSieveConsole 1.34 - 274 kp/s
proth_sieve CMOV 0.33 - 256 kp/s

http://www.aooq73.dsl.pipex.com/scores_p.htm

Since there are three "sub-projects" behind SoB (PRP, sieving, P-1 factoring), there could be some "overall" user/team stats to know who is the "best of the best"

Yes, I know, but I wanted to test it in an adverse scenario :jester: . Thanks for your great work!

More benchmarking:

-= Tualatin@10x142 W2K SP4 =-

*** "normal" ***

proth_sieve 0.31
pmin : 60000000000000
pmax : 60000010000000
# Tested p : 314507

I have run WinXP on my K6-2 at 300 MHz with 128 Mb of ram, when properly confirgured, it works well.
As Mystwalker said, P4 are good for SB, P-1 factoring and Prime95 and aren't good for sieving....

proth_sieve is finding many factors for n>20M, which are currently considered "out of range factors". Could you make these factors be recorded into another file, like "factexc20M.txt". Maybe they...

Please note that when you increase the amount of RAM available to sbfactor, it also increases the optimal bounds!
Yesterday I did a little test with 4847*2^5000007+1, by entering sbfactor 5000002...

Just download and place it in the same dir as SoBSieve, or create another one copying inside the files sobstatus.dat and sob.dat. As with sobsieve, you only need to run the exec, Before that, I...

From http://mersenneforum.org/viewtopic.php?t=862&start=0

Tualatin@10x140 MHz

-= Windows 2000 SP3 =-

proth_sieve 0.31:

proth_sieve_cmov 0.31:


SoBSieveConsole 1.34: 230 kp/s

K6-2@3x105 MHz, Win98 SE:


Wow! :eek:
SoBSieve 1.21 -> 16 kp/s
NBeGon 0.10 -> 6,6 kp/s

Thank you very much! Now, I'll benchmark it on the Tualatin.

I have tried it (some minutes), but it haven't seen any rate output... I'm too lazy to do it manually :D .
Could you add a priority level parameter?
Thanks!

Wow! It works! After factoring more than 260 k/n pairs, I've found 38372614033613527 | 22699*2^4252294+1 although it has been found too late!
:(

Factoring is the part of the project which needs, and I would say it needs urgently, more power.
If P4's are only well suite for PRPing and factoring, that doesn't means that the other processort...

Thanks Louie! At this moment, my poor Tualatin (now running@1350 MHz because my room ambient temp is 40ºC!) has factored 192 k/n pairs (many of them using 2.0 - now using 1.3 to gain speed) and 0...