Finally, after hundreds of attempts (and thousands of curves) found my first factor with ECM :smile: Even if it is only 71bits, it shows that it is possible! [M]3255283[/M]

[QUOTE=gLauss;575975]Finally, after hundreds of attempts (and thousands of curves) found my first factor with ECM :smile: Even if it is only 71bits, it shows that it is possible! [M]3255283[/M][/QUOTE]
Congrats! Nice find  may it be the first of many! 
Ryan strikes again. #11 on the all time biggest Mersenne factors [url=https://www.mersenne.ca/userfactors/any/1/bits]list[/url].
[M]M4283[/M] has a 219.268bit (67digit) factor: [url=https://www.mersenne.ca/M4283]1014581894481062086635266411284139009925301539055947709872564246847[/url] (ECM,B1=260000000,B2=3142865025316,Sigma=6655636513802850625) 
Almost....Laurv
[QUOTE=LaurV;574333]Congrats, triple 59, next one you will find will start with a quadruple 69... :razz:[/QUOTE]
Factor ends with ... let's see 1, 2, 3: 69. Exponent ends with 369; and starts with 396. Exponent has 5 out of 8 digits 6 or 9: 40% Factor has 9 out of 23 digits 6 or 9: 39%. Time found contains a 6 and a 9. [CODE]39626369 FPM1 20210416 06:19 Factor: 35172309356636629912369[/CODE] 
[QUOTE=petrw1;576000]Factor ends with ... let's see 1, 2, 3: 69.
Exponent ends with 369; and starts with 396. Exponent has 5 out of 8 digits 6 or 9: [B]40%[/B] Factor has 9 out of 23 digits 6 or 9: 39%. Time found contains a 6 and a 9. [CODE]39626369 FPM1 20210416 06:19 Factor: 35172309356636629912369[/CODE][/QUOTE] I'm pretty sure that's supposed to be 62.5% 
[QUOTE=LaurV;574333]Congrats, triple 59, next one you will find will start with a quadruple 69... :razz:[/QUOTE]TJAOI did that 7 years ago: [M]M926969327[/M] has a 49.308bit (15digit) factor: [url=https://www.mersenne.ca/M926969327]696969697584761[/url]

[QUOTE=James Heinrich;576004]TJAOI did that 7 years ago: [M]M926969327[/M] has a 49.308bit (15digit) factor: [url=https://www.mersenne.ca/M926969327]696969697584761[/url][/QUOTE]
As well as double 69 in the exponent! 
[QUOTE=James Heinrich;576004]TJAOI did that 7 years ago: [M]M926969327[/M] has a 49.308bit (15digit) factor: [url=https://www.mersenne.ca/M926969327]696969697584761[/url][/QUOTE]
[M]345495211[/M]: Factored 1163[B]69696969[/B]03 [M]608055197[/M]: Factored 23981[B]69696969[/B] 
Consecutive P1 factors with repeated ending digits
Magic_8_Ball 39629561 FPM1 20210427 14:21 Factor: 63762133812827843899999 Magic_8_Ball 39605273 FPM1 20210428 03:00 Factor: 204171204894399516952237777 
Another impressive one from Ryan (#14 on the overall biggest [url=https://www.mersenne.ca/userfactors/ecm/1/bits]list[/url], and he also got #11, #12 spots in the last 2 weeks)
[M]M4001[/M] has a 212.771bit (65digit) factor: [url=https://www.mersenne.ca/M4001]11228234992112410011165597181282604695853195021678012695442609737[/url] (ECM,B1=850000000,B2=14182957708936,Sigma=15234304705639590802) 
9/63
9 P1 factors in 63 (14.28%) attempts working on assignments with an expected success rate of 3%.

[M]M23516089[/M] has a 70.456bit (22digit) factor: [url=https://www.mersenne.ca/M23516089]1619450690983460996873[/url] (P1,B1=1200000,B2=76800000)
This is almost frustrating, as it was TF'ed to 70bit. But I really like it because the B1 is almost perfect. k= 2^2*1 175 411 *7 323 571 
Well, I decided to run a PP1 curse on my old already factored exponent.
This is my first pp1 factor P+1 found a factor in stage #2, B1=500000, B2=26500000. UID: firejuggler/Maison, M8805827 has a factor: 4175293398605056163377 (P+1, B1=500000, B2=26500000) 
P1 found a factor in stage #2, B1=740000, B2=20264000.
UID: Jwb52z/Clay, M103695649 has a factor: 2004109083829816426995592903 (P1, B1=740000, B2=20264000). 90.695 bits. 
Sadly, a composite
[M]M23517601[/M] has a 195.647bit (59digit) [b]composite[/b] (P27+P33) factor: [url=https://www.mersenne.ca/M23517601]78650091603029033018091227770166444001988216065464577593033[/url] (P1,B1=1200000,B2=79200000) 
UID: Jwb52z/Clay, M103808857 has a factor: 1401232317330993509639727923687 (P1, B1=740000),
100.145 bits. 
[M]M103830131[/M] has a 157.127bit (48digit) [b]composite[/b] (P24+P24) factor: [url=https://www.mersenne.ca/M103830131]199531333730879095999006796725214407904194653871[/url] (P1,B1=1708000)
While the composite factor itself it not extremely interesting by itself, I find it interesting because:  it was found in stage 1.  the prime factors are very similar in size (78.460 and 78.667 bits). The prime factors are 415767534785818078323247 and 479910808412848576977793. 
Nice!

M106722533 has an 110 bits factor 771972811871697820846912678000249.
Albeit 110 bits is not a joke, the factor is not a record in itself, but it is quite large and nice, considering the fact that was found in stage 1 (yes, it is [URL="https://www.mersenne.ca/exponent/106722533"]sooo smooth[/URL], like ice cream!) 
[QUOTE=LaurV;579389]M106722533 has an [STRIKE]110[/STRIKE] bits factor 771972811871697820846912678000249. [/QUOTE]
Liar! Only 109 bits, 109.25 to be more exact. :razz: 
[QUOTE=Viliam Furik;579393]Liar! Only 109 bits, 109.25 to be more exact. :razz:[/QUOTE]Why stop there? 109.25024907447 :whee:
But LaurV isn't wrong, the factor does take 110 bits to represent. You don't say it's 32.8876 decimal digits long. :smile: 
[QUOTE=Viliam Furik;579393][QUOTE=LaurV;579389]M106722533 has an [STRIKE]110[/STRIKE] bits factor 771972811871697820846912678000249. [/QUOTE]Liar! Only 109 bits, 109.25 to be more exact. :razz:[/QUOTE]Oops.
From my "I can't count" liturgy: [b]Versicle:[/b] How many bits in two to the first power? [b]Responsory:[/b] Two, two. [b]Versicle:[/b] How many decimal digits in ten to the first power? [b]Responsory:[/b] Two, two. From the output of PariGP: [code]? v=binary(771972811871697820846912678000249) %1 = [1, 0, 0, 1, 1, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 0, 1, 1, 1, 1, 0, 1, 1, 0, 0, 1, 0, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, 1, 1, 0, 1, 0, 1, 1, 0, 1, 0, 1, 0, 1, 1, 0, 1, 0, 0, 0, 1, 0, 1, 1, 1, 1, 0, 1, 0, 0, 1, 0, 1, 1, 1, 0, 0, 0, 0, 1, 1, 1, 0, 0, 1, 0, 0, 1, 1, 1, 1, 1, 0, 1, 1, 0, 0, 1, 1, 1, 1, 0, 0, 1] ? #v %2 = 110 ?[/code] 
A nice run of the mill 79 bit factor: 1025757166134493292294953
But, it was found when I poached (not sorry) a stalled P1 that was in the lowest 25 exponents for FTC. [M]103547179[/M] There are others down there that have zero check ins since assigned and are more than a month old and thus have violated the rules for Cat 0 (but the rules do seem to apply to P1 assignments down in the low FTC's)[LIST][*]Must be completed in 30 days[*]Assignments are recycled if assignment is not started with 7 days or when assignment is more than 30 days old.[/LIST] 
[QUOTE=Uncwilly;579496]There are others down there that have zero check ins since assigned and are more than a month old and thus have violated the rules for Cat 0 (but the rules do seem to apply to P1 assignments down in the low FTC's)[/QUOTE]
Just so you know, I'm working on those held by ANONYMOUS and Kas. Should all be done in about three days (assuming Colab cooperates). 
[QUOTE=chalsall;579497]Just so you know, I'm working on those held by ANONYMOUS and Kas. Should all be done in about three days (assuming Colab cooperates).[/QUOTE]
I have been working bottom up getting about 9 every 5 days. 
[QUOTE=Uncwilly;579503]I have been working bottom up getting about 9 every 5 days.[/QUOTE]
Yeah. I am aware you are on a certain team... :tu: Just wanted to declare intentions, so we didn't duplicate efforts. A Compute Cycle is a terrible thing to waste! :wink: 
[QUOTE=James Heinrich;579396]Why stop there? 109.25024907447 :whee:
But LaurV isn't wrong, [B]the factor does take 110 bits to represent[/B]. You don't say it's 32.8876 decimal digits long. :smile:[/QUOTE] Oh, didn't realize that. Sorry, LaurV. 
[QUOTE=Uncwilly;579496]A nice run of the mill 79 bit factor: 1025757166134493292294953
But, it was found when I poached (not sorry) a stalled P1 that was in the lowest 25 exponents for FTC. [M]103547179[/M][/QUOTE] Just got me another like it: [URL="https://www.mersenne.org/report_exponent/?exp_lo=103566409&full=1"]312854885986074648542201 [/URL] 78 bits The old P1 assignment had been sitting on this low Cat 0 assignment since April 18. Hadn't checked in since then. P1 is the wild west. No expiry after 30 days, no expiry after not starting in 7 days. (This was in the bottom 25 again). 
P1 found a factor in stage #1, B1=736000.
UID: Jwb52z/Clay, M104224103 has a factor: 457222887848673747662129713 (P1, B1=736000) 88.563 bits. 
Yay, I found my first top500 factor. Not even on the list yet, but soon. Albeit only at 495th place.
[M]M2315107[/M] has a 118.475bit (36digit) factor: [url=https://www.mersenne.ca/M2315107]461896913357939229136479311870224273[/url] (P1,B1=5000000,B2=505000000) 461896913357939229136479311870224273 = 2 * (2^3 * 3 * 7 * 59 * 13381 * 412537 * [B]3,978,523[/B] * [B]458,257,259[/B]) * 2315107 Also a relatively tight fit in the bounds. 
[QUOTE=Viliam Furik;580379]Yay, I found my first top500 factor[/QUOTE]:party:

[QUOTE=Viliam Furik;580379]Yay, I found my first top500 factor. Not even on the list yet, but soon. Albeit only at 495th place.
[M]M2315107[/M] has a 118.475bit (36digit) factor: [url=https://www.mersenne.ca/M2315107]461896913357939229136479311870224273[/url] (P1,B1=5000000,B2=505000000) 461896913357939229136479311870224273 = 2 * (2^3 * 3 * 7 * 59 * 13381 * 412537 * [B]3,978,523[/B] * [B]458,257,259[/B]) * 2315107 Also a relatively tight fit in the bounds.[/QUOTE] And the last fun fact to add is that it almost went unnoticed. I have run out of my worktodo, and that triggered the setting in the prime.txt that turned off the PrimeNet usage, so the factor, being found after these events, has not been reported immediately. If I didn't notice that nothing was being reported, I wouldn't have found it, and it would have been buried in the results files until deletion. Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done? Basically, I want a monologue relationship with PrimeNet; I talk to him, but he doesn't reply :grin:. 
On prime95, Advanced, manual communication, Do not contact Primenet server automatically (a box to be checked). just below there is an already checked box for 'contact now'

[QUOTE=firejuggler;580424]On prime95, Advanced, manual communication, Do not contact Primenet server automatically (a box to be checked). just below there is an already checked box for 'contact now'[/QUOTE]
I believe this would mean I'd have to manually upload every once in a while, and when I would upload, it would, in the process of contacting the PrimeNet, get some assignments back, which I don't want. Or not? 
[QUOTE=Viliam Furik;580423]Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done?[/QUOTE]
What about manually setting [C]DaysOfWork=0[/C]? That way, you'll never get automatic work and the results still will be reported normally. 
[QUOTE=Viliam Furik;580423]Is there a way to not get work from PrimeNet but not quit the PrimeNet after work is done? Basically, I want a monologue relationship with PrimeNet; I talk to him, but he doesn't reply :grin:.[/QUOTE]
NoMoreWork=1 in prime.txt 
[QUOTE=Jwb52z;577821]P1 found a factor in stage #2, B1=740000, B2=20264000.
UID: Jwb52z/Clay, M103695649 has a factor: 2004109083829816426995592903 (P1, B1=740000, B2=20264000). 90.695 bits.[/QUOTE] When I add the P1 method with B1=740000, B2=20264000 for [URL="http://factordb.com/index.php?id=1100000002602478101"]this prime in factordb[/URL], it says "Err: Calculated grouporder 2004109083829816426995592902<28> is not within B1/B2 bounds (B1=740000, B2=20264000). Please check your result!" 
[QUOTE=Uncwilly;580431]NoMoreWork=1 in prime.txt[/QUOTE]
That is the setting I am using, but it turns off the PrimeNet connection when out of work. It prints out "Successfully quit GIMPS" in the Comm thread. 
[QUOTE=kruoli;580427]What about manually setting [C]DaysOfWork=0[/C]? That way, you'll never get automatic work and the results still will be reported normally.[/QUOTE]
That may help. I'll try it. 
[QUOTE=sweety439;580439]When I add the P1 method with B1=740000, B2=20264000 for [URL="http://factordb.com/index.php?id=1100000002602478101"]this prime in factordb[/URL], it says "Err: Calculated grouporder 2004109083829816426995592902<28> is not within B1/B2 bounds (B1=740000, B2=20264000). Please check your result!"[/QUOTE]
Maybe it's got a problem with the exponent P=103695649. 2004109083829816426995592902 = 2 * 3 * 281 * 29917 * 47269 * 8106041 * 103695649, so the biggest factor is 103695649, the exponent, which is bigger than B2=20264000. Is it possible it's not accounting for the special form of Mersenne factors, which allows ignoring P as a factor of Q1 (Q is the factor found) and only using the general rules for factors found by the P1 method? 
[QUOTE=Viliam Furik;580442]Is it possible it's not accounting for the special form of Mersenne factors, which allows ignoring P as a factor of Q1 (Q is the factor found) and only using the general rules for factors found by the P1 method?[/QUOTE]
That's probably it. 
[M]M1001159[/M] has a 120.912bit (37digit) factor: [url=https://www.mersenne.ca/M1001159]2500439903769890259112379635985290039[/url] (P1,B1=10000000,B2=1110000000)
Is it Christmas already? This one should come in at about 365th place. 
No, no, no, I have no budget for christmass right now. So it is NOT christmass. At least for another 6 month.

[QUOTE=Viliam Furik;580523][M]M1001159[/M] has a 120.912bit (37digit) factor: [url=https://www.mersenne.ca/M1001159]2500439903769890259112379635985290039[/url] (P1,B1=10000000,B2=1110000000)
Is it Christmas already? This one should come in at about 365th place.[/QUOTE] You have bet my best. I am in the 120 bit club too. Very nice catch. :faf: 
M[M]23554211[/M] has a 114.027bit (35digit) factor: [URL="https://www.mersenne.ca/M23554211"]21164767805799094411604254592575543[/URL] (P1,B1=1200000,B2=79200000)
I also have a near Christmass time 
We found both an [URL="https://www.mersenne.ca/exponent/35124833"]98.x[/URL] and [URL="https://www.mersenne.ca/exponent/35123269"]101.x[/URL] bits factors in 35.1M range, [STRIKE]what's worth mentioning them is the fact they were both found in a row, one after the other, and both found [U]in stage 1[/U] (!)
They are not sync'd on James' site yet, but they are indeed very smooth![/STRIKE] 
[QUOTE=LaurV;580844]We found both an [URL="https://www.mersenne.org/report_exponent/?exp_lo=35120669&full=1"]98.x[/URL] and [URL="https://www.mersenne.org/report_exponent/?exp_lo=35124833&full=1"]101.x[/URL] bits factors in 35.1M range, what's worth mentioning them is the fact they were both found in a row, one after the other, and both found [U]in stage 1[/U] (!)
They are not sync'd on James' site yet, but they are indeed very smooth![/QUOTE] Your 98.x factor directs to 83.x factor and 101.x factor directs to 98.x factor. 
Fixed, thank you very much! (I didn't edit the quote in your post, only my post). I got lost in so many factors and links. But in this case, the 101 is not anymore "smooth". My mistake. As they were not yet on mersenne.ca at the time, I wrongly remembered their size (which is displayed when reporting), and I assumed the 101 was the smooth one (the "smoothness" is deduced from the amount of credit given, you don't need to do any calculation or to see the k value to know your factor is very smooth, hehe).
Therefore, to repair the damage, take this new [URL="https://www.mersenne.ca/exponent/35126153"]115 bits[/URL] guy here... :razz: 
[QUOTE=sweety439;580439]When I add the P1 method with B1=740000, B2=20264000 for [URL="http://factordb.com/index.php?id=1100000002602478101"]this prime in factordb[/URL], it says "Err: Calculated grouporder 2004109083829816426995592902<28> is not within B1/B2 bounds (B1=740000, B2=20264000). Please check your result!"[/QUOTE]Um, I don't know how to check the result. I just report what the screen and results file shows me.

P1 found a factor in stage #2, B1=737000, B2=20466000.
UID: Jwb52z/Clay, M104363929 has a factor: 12877212261710761007261993 (P1, B1=737000, B2=20466000), 83.413 bits. 
P1 found a factor in stage #1, B1=739000.
UID: Jwb52z/Clay, M104656151 has a factor: 179821323726211482179833 (P1, B1=739000) 77.251 bits. 
one of my biggest find
[M]M35821609[/M] has a 114.854bit (35digit) factor: [url=https://www.mersenne.ca/M35821609]37533512686961073352872057770174521[/url] (P1,B1=1200000,B2=73200000) 
P1 found a factor in stage #1, B1=739000.
UID: Jwb52z/Clay, M104679433 has a factor: 7144991229022485833889497 (P1, B1=739000) 82.563 bits. 
P1 found a factor in stage #2, B1=739000, B2=20534000.
UID: Jwb52z/Clay, M104710483 has a factor: 2087604414043709000130191 (P1, B1=739000, B2=20534000) 80.788 bits. 
P1 found a factor in stage #1, B1=10000000.
M524351 has a factor: 210100758636629488891459910447 (P1, B1=10000000) This 97.407bit factor is notable because it's my first P1 Mersenne factor. 
[QUOTE=Happy5214;582582]This 97.407bit factor is notable because it's my first P1 Mersenne factor.[/QUOTE]Congrats, and may you find many more! :smile:

M23851277 has a factor: 2172095945184050340167 [TF:70:71*:mfaktc 0.21 barrett76_mul32_gs]
found 1 factor for M23851277 from 2^70 to 2^71 (partially tested) [mfaktc 0.21 barrett76_mul32_gs] k=3 989 × 11 414 932 211 A not at all smooth k ( found with mfaktc) 
P1 found a factor in stage #2, B1=755000, B2=20983000.
UID: Jwb52z/Clay, M104819381 has a factor: 574983783644612576435518337 (P1, B1=755000, B2=20983000) 88.894 bits. 
P1 found a factor in stage #1, B1=756000.
UID: Jwb52z/Clay, M104890637 has a factor: 126027633778180756401977 (P1, B1=756000) 76.738 bits. 
I have almost bested myself...
[M]M1030361[/M] has a 120.867bit (37digit) factor: [url=https://www.mersenne.ca/M1030361]2424326756295464099182822578592235663[/url] (P1,B1=10000000) But still a big factor! Now I have two top500 entries. :party: 
[QUOTE=Viliam Furik;583654]Now I have two top500 entries.
[/QUOTE] :tu: Paraphrasing James, congrats and may you have many more in the future! 
P1 found a factor in stage #1, B1=759000.
UID: Jwb52z/Clay, M105269581 has a factor: 6228935338450361187678798473 (P1, B1=759000) 92.331 bits. This is the highest bit level one I've had in a while, especially in stage 1. 
[QUOTE=Jwb52z;584151]92.331 bits. This is the highest bit level one I've had in a while, especially in stage 1.[/QUOTE]Since [url=https://www.mersenne.ca/userfactors/pm1/789/date]early May[/url].

[QUOTE=LaurV;583728]:tu: Paraphrasing James, congrats and may you have many more in the future![/QUOTE]
Sure did! [M]M1055471[/M] has a 123.071bit (38digit) factor: [url=https://www.mersenne.ca/M1055471]11172871966337160594575665335374991233[/url] (P1,B1=10000000,B2=1000000000) My new personal record, about 288th place in the top 500 when it's updated. :party: 
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! [URL="https://www.mersenne.ca/exponent/836683"]M836683[/URL].

These 500K exponents are a gold mine.
[M]M538751[/M] has a 132.045bit (40digit) factor: [url=https://www.mersenne.ca/M538751]5617865834413045127033000770286991147617[/url] (P1,B1=10000000,B2=1110000000) New personal best! :party: I am doing the P1 with bounds as mentioned > B1=10,000,000, B2 is automatic. This results in about 1.35 GHzD 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... 
[QUOTE=Viliam Furik;585115][M]M538751[/M] has a 132.045bit (40digit) factor: [URL="https://www.mersenne.ca/M538751"]5617865834413045127033000770286991147617[/URL] (P1,B1=10000000,B2=1110000000)
New personal best![/QUOTE] Yay! Well done! :tu: Congrats! 
[QUOTE=Viliam Furik;585115]These 500K exponents are a gold mine.
[M]M538751[/M] has a 132.045bit (40digit) factor: [url=https://www.mersenne.ca/M538751]5617865834413045127033000770286991147617[/url] (P1,B1=10000000,B2=1110000000) New personal best! [...] I am doing the P1 with bounds as mentioned > B1=10,000,000, B2 is automatic. This results in about 1.35 GHzD 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...[/QUOTE] Glad you're getting mileage (or whatever the SI equivalent is) from the 500K range. I only found one factor from the whole 520K525K range (mentioned in a previous post in this thread) using the worktodogenerating Python script. 
[QUOTE=Happy5214;585170]Glad you're getting mileage (or whatever the SI equivalent is) from the 500K range. I only found one factor from the whole 520K525K range (mentioned in a previous post in this thread) using the worktodogenerating Python script.[/QUOTE]
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 P1, but I went to 500K because I thought those should also be lifted. 
[QUOTE=Viliam Furik;585189]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 P1, but I went to 500K because I thought those should also be lifted.[/QUOTE] 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 GHzday credit on my P1 tasks.) 
[QUOTE=Happy5214;585214]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 GHzday credit on my P1 tasks.)[/QUOTE]
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 [URL="https://www.mersenne.ca/morefactors.php"]here[/URL]. 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... 
[QUOTE=Viliam Furik;585219]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 [URL="https://www.mersenne.ca/morefactors.php"]here[/URL]. 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...[/QUOTE] No, I used [url]https://github.com/keisentraut/prime95optimalworktodo[/url], which leaves B2 blank (letting mprime determine it). However, it also adjusts the TF field in the worktodo based on the ECM level, so I think I was getting lower B2's since there was more ECM work done (and thus a higher implicit TF level). My max RAM allocation for that instance is 32 GB, and it never got close to that while I was doing that range. 
M5210099 has a factor: 2944892728119316210127 (P1, B1=2500000, B2=207500000) (71.319 bits)
It's puny, I know, but I'm fond of it because it's my first nonECM stage 2 Mersenne factor. My previous P1 and P+1 factors were both found in stage 1. 
[URL="https://www.mersenne.org/report_exponent/?exp_lo=23243107&full=1"]M23243107 [/URL] has three factors in the TF71 range. It's kind of a curiosity.
I happened to find 2 factors in one TF range several times, but 3 for the first time! 
[QUOTE=Miszka;585698][URL="https://www.mersenne.org/report_exponent/?exp_lo=23243107&full=1"]M23243107 [/URL] has three factors in the TF71 range. It's kind of a curiosity.
I happened to find 2 factors in one TF range several times, but 3 for the first time![/QUOTE] Not so long ago I had a brief discussion with user tuckerkao about the possibility of this happening... Nice luck! 
[QUOTE=Miszka;585698][URL="https://www.mersenne.org/report_exponent/?exp_lo=23243107&full=1"]M23243107 [/URL] has three factors in the TF71 range. It's kind of a curiosity.[/QUOTE]But not as rare as you might think. There are >2500 such examples in GIMPS range (but only 6 new examples have been found so far in 2021).
There are (so far) only 7 examples where there are [b]4[/b] known factors in the same bitlevel: [m]33218089[/m], [m]128757283[/m], [m]143570279[/m], [m]234616103[/m], [m]563950589[/m], [m]578590853[/m], [m]946287211[/m] 
[QUOTE=James Heinrich;585702]But not as rare as you might think. There are >2500 such examples in GIMPS range (but only 6 new examples have been found so far in 2021).
There are (so far) only 7 examples where there are [b]4[/b] known factors in the same bitlevel: [m]33218089[/m], [m]128757283[/m], [m]143570279[/m], [m]234616103[/m], [m]563950589[/m], [m]578590853[/m], [m]946287211[/m][/QUOTE] These 7 examples have a fairly low bitlevel and it will be rather very difficult to find similar ones with a bitlevel above 70some 
P1 found a factor in stage #2, B1=760000, B2=20835000.
UID: Jwb52z/Clay, M105530011 has a factor: 700781945616999543935075224151 (P1, B1=760000, B2=20835000) 99.145 bits. 
Not mine, but a pretty triple factor:
[M]M105587893[/M] has a 236.753bit (72digit) [b]composite[/b] (P23+P24+P26) factor: [url=https://www.mersenne.ca/M105587893]186125867355522179214500290117704070927566484401081129960541990698683479[/url] (P1,B1=823000) 
[QUOTE=James Heinrich;586092]Not mine, but a pretty triple factor:
[M]M105587893[/M] has a 236.753bit (72digit) [b]composite[/b] (P23+P24+P26) factor: [url=https://www.mersenne.ca/M105587893]186125867355522179214500290117704070927566484401081129960541990698683479[/url] (P1,B1=823000)[/QUOTE] That's pretty sublime. 
Nice! That is a beauty! I didn't found a triple yet.
Congrats to the founder! (Kriesel) 
The smaller with 76.191 bits is close to the 76 bit range for such exponents :smile:

[M]M1897121[/M] has a 77.294bit (24digit) factor: [URL="https://www.mersenne.ca/M1897121"]185310913945752397948441[/URL] (ECM,B1=50000,B2=6750000) < the 9th known factor
[M]M194653[/M] has a 119.349bit (36digit) factor: [URL="https://www.mersenne.ca/M194653"]846314715301812068679342636153284159[/URL] (ECM,B1=1000000,B2=135000000) < the 9th known factor [M]M599803[/M] has a 106.747bit (33digit) factor: [URL="https://www.mersenne.ca/M599803"]136181509257226777136568353013047[/URL] (ECM,B1=3000000,B2=528000000) < [B]the 10th known factor[/B]! I'll run more curves on them, maybe I get lucky and beat the current record of 11 known factors. 
Wow, very nice!

New P+1 factor: 67111165753873384058235537928247 for M[M]5210563[/M] (B1=1,250,000, start=2/7) (105.726 bits)
It's my largest nonECM factor ever and just half a bit off my personal best. All from stage 1 with low (but recommended) bounds. Plus it's the first factor for that exponent. 
[QUOTE=Happy5214;586460]New P+1 factor: 67111165753873384058235537928247 for M[M]5210563[/M] (B1=1,250,000, start=2/7) (105.726 bits)[/QUOTE]
Wow! That is one supersmooth factor. 
[QUOTE=Happy5214;586460]New P+1 factor: 67111165753873384058235537928247 for M[M]5210563[/M] (B1=1,250,000, start=2/7) (105.726 bits)
It's my largest nonECM factor ever and just half a bit off my personal best. All from stage 1 with low (but recommended) bounds. Plus it's the first factor for that exponent.[/QUOTE] :bow: 
[M]M111298777[/M] has a factor: 135398831970267435540791 (76.842 bits)
k = 5 × 23 × 37 × 313 × 1069 × 427241 Another P1 smooth factor found by TF. 
[QUOTE=Zhangrc;586546][M]M111298777[/M] has a factor: 135398831970267435540791 (76.842 bits)[/QUOTE]
[M]M111298699[/M] has a factor: 82602996758522984927977 (76.129 bits) 2 factors were found out of 22 trials in the 111.2M range. That's lucky enough, for there were some time when I tested more than 500 exponents without finding a single factor. :bounce: 
P1 found a factor in stage #1, B1=762000.
UID: Jwb52z/Clay, M105693659 has a factor: 215018688290325922746529 (P1, B1=762000) 77.509 bits. 
I was running a few ECM small assignments and a factor turned up.
Sigma=5667910856171759, B1=50000, B2=5000000. M2088329 has a factor: 185217242100981866539823 24 digits, 77.3 bits k = 197 * 1237 * 181977029831 
M[M]5211229[/M] gave me a 114.058bit P1 factor (21623513459060090628814036845352337) (an alltime personal best by almost 8 bits) [I]and[/I] a separate 90.559bit stage 1 P+1 factor (1824415976895261507796344041).

[QUOTE=Happy5214;586838]M[M]5211229[/M] gave me a 114.058bit P1 factor (21623513459060090628814036845352337) (an alltime personal best by almost 8 bits) [I]and[/I] a separate 90.559bit stage 1 P+1 factor (1824415976895261507796344041).[/QUOTE]
That's Totally BEAUtiful! Congrats! 
[QUOTE=Happy5214;586838]M[M]5211229[/M] gave me a 114.058bit P1 factor (21623513459060090628814036845352337) (an alltime personal best by almost 8 bits) [I]and[/I] a separate 90.559bit stage 1 P+1 factor (1824415976895261507796344041).[/QUOTE]
Those were both logged in the 2 PM local (America/Chicago) hour Sunday, while I was sleeping (I didn't wake up until after 7 PM local Sunday night). Less than 11 hours later, just after 1 AM local Monday, I beat my personal best again: 275190978175938200476768961501749313 for M[M]5211289[/M] (B1=2,500,000, B2=240,000,000) (117.728 bits) Sadly, no bonus P+1 hit for this one. 
[M]M6282557[/M] has a 112.036bit (34digit) factor: [url=https://www.mersenne.ca/M6282557]5324115842154238964583982961636201[/url] (P1,B1=3000000,B2=90000000)
Quite nice one, and first found in that range for me. 
My CPUs have mostly been busy doing other stuff for months, so I was mildly excited to see my first P1 factor since June:
[M]M105233789[/M] has a 92.789bit (28digit) factor: [url=https://www.mersenne.ca/M105233789]8554126736286122188536749441[/url] (P1,B1=820000,B2=34707000) Only to discover it had been lingering in worktodo for too long and had apparently expired and someone else found the factor two weeks ago. :picard: 
My list of factors for numbers in the 200 million digit range (M7593XXXXX to be specific)
Disclaimer: You may not see these in mersenne.ca, but this is probably because I self assigned them.
[URL="https://www.mersenne.org/report_exponent/?exp_lo=759376643&full=1"]M759376643[/URL] factor: 14247797623131731084353 [URL="https://www.mersenne.org/report_exponent/?exp_lo=759376729&full=1"]M759376729[/URL] factor: 4094254204485992428199 [URL="https://www.mersenne.org/report_exponent/?exp_lo=759376843&full=1"]M759376843[/URL] factor: 3509297005626164059583 ______________________________________________________________________________________________________ :google: 
All times are UTC. The time now is 17:30. 
Powered by vBulletin® Version 3.8.11
Copyright ©2000  2023, Jelsoft Enterprises Ltd.