P-1 coordination thread - discussion

[engracio]

Interesting lets compare Louis and yours...

12250000 12500000 louie 107
11780000 11930000 louie 44

Basically Louie P-1'ed a range of 400000 n and produced 151 factors.

0.3775 factors per 1000 n-range

11600000 11770000 engracio 30
12000000 12020000 engracio 8
11400000 11600000 engracio 51

E P-1'ed a total range of 390000 n and produced 89 factors.

0.228 factor per 1000 n-range.

Louie used a B1=95K with B2=B1x11.5
E used a B1=75K with B2=B1x11

Basially Louie spent close to 30% more processing power per k/n pair, yeilding a 65% increase in factor probability.

-------------------

Very interesting, E you might want to try higher bounds say B1=110k and if you are not limited in memory and have dual channel try upping your B2:B1 ratio. I wouldn't go much beyond 14.

B2=1500000

Are you still running those MPX's?

The most important point to remember is a little P-1 is better than no P-1 so as long as we are not passing ranges...

Vjs,

Yes on the MPX but they are now sieving and dying slowly, had to use their memory and to increase and make it dual channel the memory on the Xeons and a Pentium D915 oc'd to 3500 mhz. Probably could get a few more mhz but did not want to spent money on memory and better cooling.

Did not know you guys were going to break it down and throw off my galactic wag. Portions of my range were skipped due to the random fluctuations of the prp. I know I skipped a few factors.

I really just wanted to know how Louie was able to complete those range so quick. One quick answer was he had more machines to crunch. doh!

I'll slowly increase the B2 and see if they really make that much difference. My P1 machines are all Intel cpu's and I try to have at least 1gb of memory while factoring. What is odd is I have P4 2.8 with only 512 memory with 452mb allotted, max memory Prime95 would let me allocate. It can crunch a factor every two hours but my Xeon 3.1 could only crunch every two and half with 560mb alloted per instance.

Most of the time it is not used. Ummm.

e

[vjs]

Humm,

I forgot about that in the calc's I guess that throws everything out the window from above.

Still using my MPX as a home machine, dual 2.4G Bartons and 2G of ram, sieve exclusively. Yup it's getting old. I should have sold it off 6 months ago. I could have got ~$400 for just the board and processors . But it's tough to find something decent with u320 or PCI-X slots.

[glennpat]

Since this thread is a little old what is the sieving depth and factor value should be used when doing a range?
Thanks.

[vjs]

I wouldn't use sieve depth and factor worth.
I'd simply specify the B1 and B2 values.

Since it will be a while until we get to 14M I would suggest you use.

B1=100k to 120k with a b2=b1x12 to b2=b1x14 depending on how much memory you have.

in other words,

minimum
B1=100000 b2=1200000

maximum
B1=120000 b2=1700000

What CPU memory and amount of memory do you have?

[glennpat]

The one I will run on is an Intel dual core 6600 running 2.4 GHz (stock) with 2 Gig of memory. SOB Sieve will also be running on it.

To use the B1 B2 do I use the AdvanceFactor command for PRIME95? I assume I edit the the worktodo.ini to use the B1 B2.

[Joe O]

To specify the desired B1 and B2 values, place the following line(s) in your worktodo.ini file:
Pminus1=10223,2,14000237,1,120000,1700000
where
Pminus1=k,2,n,1,B1,B2

Do not use the AdvanceFactor command, that is for something else.

[glennpat]

Thank You! I now see that was in the instructions at the top of the reserve thread.

The 1st few line of my are worktodo are:

Pminus1=21181,2,14000180,1,120000,1700000
Pminus1=10223,2,14000237,1,120000,1700000
Pminus1=21181,2,14000252,1,120000,1700000
Pminus1=10223,2,14000261,1,120000,1700000
Pminus1=55459,2,14000278,1,120000,1700000

It is running.