fond of a factor? Burn yourself to become remains

[LaurV]

Originally Posted by Viliam Furik

Now I have two top-500 entries.

Paraphrasing James, congrats and may you have many more in the future!

[Jwb52z]

P-1 found a factor in stage #1, B1=759000.
UID: Jwb52z/Clay, M105269581 has a factor: 6228935338450361187678798473 (P-1, B1=759000)

92.331 bits. This is the highest bit level one I've had in a while, especially in stage 1.

[James Heinrich]

Originally Posted by Jwb52z

92.331 bits. This is the highest bit level one I've had in a while, especially in stage 1.

Since early May.

[Viliam Furik]

Originally Posted by LaurV

Paraphrasing James, congrats and may you have many more in the future!

Sure did!

M1055471 has a 123.071-bit (38-digit) factor: 11172871966337160594575665335374991233 (P-1,B1=10000000,B2=1000000000)

My new personal record, about 288th place in the top 500 when it's updated.

[gLauss]

Found a nice P+1 factor, with 101 bits it is currently in the top 10 of Mersenne factors found by P+1. And k is prime, too! M836683.

[Viliam Furik]

These 500K exponents are a gold mine.

M538751 has a 132.045-bit (40-digit) factor: 5617865834413045127033000770286991147617 (P-1,B1=10000000,B2=1110000000)

New personal best!


I am doing the P-1 with bounds as mentioned -> B1=10,000,000, B2 is automatic. This results in about 1.35 GHz-D of work, on average. If anyone wants to look for potentially really big factors, I recommend B1=25,000,000, at least. I think I am going to change it to that value right now...

[LaurV]

Originally Posted by Viliam Furik

M538751 has a 132.045-bit (40-digit) factor: 5617865834413045127033000770286991147617 (P-1,B1=10000000,B2=1110000000)

New personal best!

Yay! Well done!
Congrats!

[Happy5214]

Originally Posted by Viliam Furik

These 500K exponents are a gold mine.

M538751 has a 132.045-bit (40-digit) factor: 5617865834413045127033000770286991147617 (P-1,B1=10000000,B2=1110000000)

New personal best!

[...]

I am doing the P-1 with bounds as mentioned -> B1=10,000,000, B2 is automatic. This results in about 1.35 GHz-D of work, on average. If anyone wants to look for potentially really big factors, I recommend B1=25,000,000, at least. I think I am going to change it to that value right now...

Glad you're getting mileage (or whatever the SI equivalent is) from the 500K range. I only found one factor from the whole 520K-525K range (mentioned in a previous post in this thread) using the worktodo-generating Python script.

[Viliam Furik]

Originally Posted by Happy5214

Glad you're getting mileage (or whatever the SI equivalent is) from the 500K range. I only found one factor from the whole 520K-525K range (mentioned in a previous post in this thread) using the worktodo-generating Python script.

I am searching all factored exponents starting from 500,009 and increasing their bounds to 10,000,000. For the next ones, I switched to 20,000,000, which means fewer exponents per day, but a higher chance of factors. Based on the results, I will decide whether to switch back or continue with 20 million.

I am planning on getting to 1M exponents someday, where I've already started P-1, but I went to 500K because I thought those should also be lifted.

[Happy5214]

Originally Posted by Viliam Furik

I am searching all factored exponents starting from 500,009 and increasing their bounds to 10,000,000. For the next ones, I switched to 20,000,000, which means fewer exponents per day, but a higher chance of factors. Based on the results, I will decide whether to switch back or continue with 20 million.

I am planning on getting to 1M exponents someday, where I've already started P-1, but I went to 500K because I thought those should also be lifted.

I've moved up to the 5.21M range for my next batch (based on the number in my user name), so there shouldn't be any conflicts between us. There's less ECM in that range too, so the B2's generated by that Python script should be higher. (I noticed your B2 was a bit higher than mine, and I was getting slightly under 1 GHz-day credit on my P-1 tasks.)

[Viliam Furik]

Originally Posted by Happy5214

I've moved up to the 5.21M range for my next batch (based on the number in my user name), so there shouldn't be any conflicts between us. There's less ECM in that range too, so the B2's generated by that Python script should be higher. (I noticed your B2 was a bit higher than mine, and I was getting slightly under 1 GHz-day credit on my P-1 tasks.)

It depends on the allocated RAM, and other things, so allowing ~2.5 GB of RAM per worker probably makes the difference.

Meanwhile...
Oh, you generated your B2s yourself. I let Prime95 generate them. So that's probably the main difference.

You can simply use this tool on mersenne.ca here. You can set your exponent range and B1, and it will generate worktodo lines for you. You only need to delete those which already had a bigger B1 done. Or use a script for them...