My first P-1 factor:

UID: slandrum/BB2, M115047523 has a factor: 26766179697464143575646837913 (P-1, B1=846000, B2=25442000, E=6)

94.4 bits

:groupwave:

M[M]107476399[/M] has a factor: 15352799235581412298952661367

Nothing impressive for P-1 (94 bits) but my last F-PM1 was almost 100 tests ago. I was starting to think I had a hardware problem.

[QUOTE=techn1ciaN;593769]M[M]107476399[/M] has a factor: 15352799235581412298952661367

Nothing impressive for P-1 (94 bits) but my last F-PM1 was almost 100 tests ago. I was starting to think I had a hardware problem.[/QUOTE]

Been there.
Over 56,000 attempts I average a factor every 30 or 40 but have seen stretches as high as 373 with no factor....and every time I have a bad stretch I still want to suspect the hardware....then they snap out of it and make up for lost time.

Patience is a virtue. :whistle:

Two factors found while DC PM1'ing exponents with poor (stage 1 only) PM1 :smile:

[M]59794643[/M] with factor 758607030356942234110073 (79.328 bits)


[M]60167521[/M] with factor 108612809058959125048583449 (86.489 bits)

[QUOTE=axn;593383]Time to upgrade?[/QUOTE]

I probably will when the stable version is available!

My first P+1 factor and even a relatively large one and a relatively smooth one and of a relatively small Mersenne number:

[CODE][URL="https://www.mersenne.ca/exponent/211231"]M211231[/URL]
Start=2/7, B1=150,000,000, Factor: 44020293565604983870643000656007 (32 digits, 105.1 bits)
P+1 = 2^3 * 3 * 17^2 * 83 * 157 * 2441 * 258337 * 17578577 * 43936757[/CODE]

M[M]997577587[/M] has a factor: 11562860692189321253647

M[M]997571873[/M] has a factor: 18373625784649599011423

M[M]997570663[/M] has a factor: 14100309041276501026441

M[M]997564333[/M] has a factor: 13823818175199038095129

M[M]997561469[/M] has a factor: 17272242508747031148527

M[M]997557647[/M] has a factor: 18246811250485963666177

M[M]997557367[/M] has a factor: 13755089029976709478417

M[M]997555331[/M] has a factor: 13188178428948819158353

I usually TF at the DC wavefront, but I've been having a dry streak of more than 300 exponents there. I loaded about 600 of these 997,xxx,xxx exponents as a hardware sanity check since they run so quickly at current TF levels. Conclusion: lack of DC luck is indeed just that, bad luck.

Interestingly, my throughput in GHz-days / day is substantially better with DC-range exponents (60–65 M) than with these huge 997 M ones — appx. 970 versus appx. 850. I optimized my MFaktC config by trial and error with a DC-range test exponent, so I thought this might be an artifact of that, but I tried various tweaks and none produced an improvement.

Another one, 37 digits, the largest one found by P+1 so far, though admittedly it was found at the P-1 part (it's not P+1 smooth at all).

[CODE][URL="https://www.mersenne.ca/exponent/214069"]M214069[/URL]
Start=2 / 7, B1=150000000, B2=12750000000, Factor: 1765947009958424280438725602396032049 (37 digits, 120.4 bits)
P+1 = 2 * 5^2 * 101 * 31723 * 2573471 * 4283440708731964743577
k = 2^3 × 3^2 × 7^2 × 29 × 31 × 757 × 68687 × 3287507 × 7607965061[/CODE]

Feels like I've saved a lamb from the slaughter on this one:
[M]107415289[/M] (factor=67834286362972615909729897, 85.871 bits), it was expired as a PRP test and assigned (very close to cat 0, but still cat 1) to me as P-1, I prioritized it and ran it with tests_saved=1 as to make it less likely to hold up a milestone down the line!


Also, TF came up with a factor today:
[M]108617059[/M] (factor=144166210879913180106767, 76.932 bits)

P-1 found a factor in stage #2, B1=794000, B2=21764000.
UID: Jwb52z/Clay, M108035089 has a factor: 130233006903988384213171714266285847938196943239024729226893649081 (P-1, B1=794000, B2=21764000)
I know it's a composite factor. Unbroken it's a whopping 216.306 bits. It can be broken down into these two factors: 6384544128130228761451969, which is 82.401 bits and 20398168497290705231363540518336781235449, which is 133.906 bits.