Hi All! Even though I haven't been around these parts much lately I am a very old hand at SOB who started when the project started. I post here to ask for your assistance on a study of DC volunteers...
Type: Posts; User: garo
Hi All! Even though I haven't been around these parts much lately I am a very old hand at SOB who started when the project started. I post here to ask for your assistance on a study of DC volunteers...
Rosebud,
run.sh invokes sbfactor. So you need to redirect the output of sbfactor. Try to edit run.sh and it should work.
Factoring has it's own ranking so there are in effect two projects where you can watch your rank climb. You guys are about 1200 in the factoring ranks right now. The exact number is unavailable as...
Word usually does not take up a lot of CPU. Instead it is more likely that your problem was due to memory usage. Check how much memory you have allocated to Prime95. The P-1 factoring is very memory...
If you are LL testing or doublechecking, I find that my 2.53GHz P4 does approximately 0.01 P90 CPUyears/hr. That translates to about 1.68yrs/week.
I think that this is just a bad idea! Skipping ranges may speed up the rate at which we get factors but it will be real hard to keep track of the skipped ranges if we want to sieve them in the future...
Troodon,
Yes it should be fine. However, since you are changing the factor value parameter to 2.0 the bounds will increase and some work will need to be redone for the numbers you have already...
I've been watching the progress for some days now and the "real" assigned max usually goes up by 8-10000 a day. With that in mind I think a safe guess is 4020000.
So do your range :)
Hi Mike and Louie,
The factors I submitted without logging in have not been credited yet. Any ETA on this?
thanks
488399926097359 | 4847*2^4026567+1
1863592358663911 | 10223*2^4029221+1
51314675885537 | 19249*2^4026722+1
Hi Louie,
I forgot to log on as I submitted these three factors today.I...
I have switched to a 1.2 factor value for my current range as proth tests are catching up with the P-1 effort pretty fast.
Some more excel work. I tried to compute the average time it will take to complete a test with the preceding probabilities and times to test. Of course, sbfactor is now picking optimal bounds and...
As a followup, I rustled up a quick spreadsheet to tell us what will be the rate of finding factors for given "factor values" - factor value is the argument to sbfactor that says how valuable the...
I think we need to use 1.0 and low bounds from now on otherwise prp will catch up pretty soon. We need to be doing 500 or so P-1 tests everyday. We need more machines!!
Finally!!
Found a factor
127404468919821091 | 19249*2^4003538+1
127404468919821090 = 2 * 3 * 5 * 19 * 67 * 71 * 227 * 2731 * 75793
smh,
I think it is overestimating even after taking that into account.
As an example, my P4 2533 takes 76 minutes to do a P-1 with the doublechecking flag on i.e. when it should not take the...
I am still convinces that the bounds estimation routine is overestimating the cost of an LL test. I wish I could be more specific but I've looked at the common.c code several times and I cannot see...
I think that the current bounds are suboptimal. That is probably the reason why factors are not being found fast enough. And of course, sieving is still more efficient. But P-1 gives us the...
I looked at the data that ceselb had posted. Unfortunately it is not very useful in figuring out optimal bounds as most factors are not P-1 smooth.
For instance, a B2 bound of 1 million would...
Hi Louie,
You are right -x 50 was not the right way. In fact I did not employ that technique after all and used the doublecheck flag as you have just suggested.
Using double-check on lowered...
Yes, I'm getting similarly long times. I got 7 hours to finish a test on a P4-2533. Given that the chance of finding a factor is 3% this implies 7*33 /24 = 9 days to finish two PRP tests - one for...
Woo hoo! I'm number 2 in the stats!!!:|party|:
Ah I better enjoy it till the stats are fixed.
It's an original factor - didn't find it in the latest files posted by Louie and the n was listed as uncleared in one of the lists posted recently.
It took me about 5 hours on an Athlon 1333...
961094450858074349 | 67607*2^4022171+1
Just wanted to report a real big useful factor!!
What does your model say about stopping sieving at once? How would the time required to get to the three primes change then?