fond of a factor? Urn yourself to become remains - Page 71

c10ck3r · 2013-08-07, 03:26

Quote:

Originally Posted by Prime95

Is that a GIMPS P-1 record?

Most likely not. http://www.mersenne.ca/exponent.php?...tails=17504141
Seems like a good candidate for that title. 148.257 bits, slightly larger 45 digit prime. (It is largest reported between 10M and 100M)

Jwb52z · 2013-08-07, 04:02

P-1 found a factor in stage #1, B1=755000.
UID: Jwb52z/Clay, M69601027 has a factor: 1404142018250675959530553

80.216 bits.

Jwb52z · 2013-08-07, 21:29

P-1 found a factor in stage #2, B1=725000, B2=16131250.
UID: Jwb52z/Clay, M67001843 has a factor: 3233475844526407689088897

81.419 bits.

cheesehead · 2013-08-12, 05:58

M13121657 has a factor: 45685540395703619321
k = 2² × 5 × 7 × 13 × 956508209

Jwb52z · 2013-08-13, 16:13

P-1 found a factor in stage #2, B1=725000, B2=16131250.
UID: Jwb52z/Clay, M67029509 has a factor: 5347973969691118904158777

82.145 bits.

Uncwilly · 2013-08-15, 23:32

332312179 has a factor of 14210518201851118532927. I ran it from 61 to 64 one day in 2009, came back months later, ran it to 66, a month after that ran it to 67, months after that, took it to 70. After some other folks touched it over the years, I worked on it again and found the factor at 73.6 bits.

Jwb52z · 2013-08-21, 13:39

P-1 found a factor in stage #1, B1=725000.
UID: Jwb52z/Clay, M67058449 has a factor: 12003053851265177348924609

83.312 bits.

P-1 found a factor in stage #1, B1=550000.
UID: Jwb52z/Clay, M62826059 has a factor: 6971119617292915006902751

82.528 bits.

Jayder · 2013-08-22, 17:03

Not sure if this thread is for this type of work, but I am happy about my 20th factor in this range. If it's not welcome say so and I'll refrain from posting further.

Two months, 2367 exponents, 20 factors.

Code:

Type	exponent	factor			date		Factor Bits
TF	M3,961,813	12556174496306564471	23 Jun 2013	63.4450
TF	M3,962,759	9261589965653852479	24 Jun 2013	63.0060
TF	M3,964,801	9664758239092017583	25 Jun 2013	63.0674
TF	M3,977,867	9333734548426688497	4 Jul 2013	63.0172
TF	M3,984,611	9727264321022045023	9 Jul 2013	63.0767
TF	M3,987,943	15865097197661369353	11 Jul 2013	63.7825
TF	M3,993,229	15697820045761779689	15 Jul 2013	63.7672
TF	M3,996,281	16232132088556504873	16 Jul 2013	63.8155
TF	M4,002,727	15869623269597059671	19 Jul 2013	63.7829
TF	M4,010,143	11458024374840134951	24 Jul 2013	63.3130
TF	M4,014,767	13876869518095649927	27 Jul 2013	63.5893
TF	M4,019,083	13905515972585089847	30 Jul 2013	63.5923
TF	M4,023,749	13310358497560331287	3 Aug 2013	63.5292
TF	M4,036,391	11119405417589098039	9 Aug 2013	63.2697
TF	M4,048,481	17741041830373275551	15 Aug 2013	63.9437
TF	M4,051,057	16801786620416341871	16 Aug 2013	63.8652
TF	M4,060,663	15346636721256778151	20 Aug 2013	63.7346
TF	M4,065,203	18383033151647681551	21 Aug 2013	63.9950
TF	M4,066,597	16230472112019316703	21 Aug 2013	63.8153
TF	M4,067,831	11349032901921126673	22 Aug 2013	63.2992

c10ck3r · 2013-08-22, 20:20

Quote:

Originally Posted by Jayder

Not sure if this thread is for this type of work, but I am happy about my 20th factor in this range. If it's not welcome say so and I'll refrain from posting further.

Two months, 2367 exponents, 20 factors.

Code:

Type    exponent    factor            date        Factor Bits
TF    M3,961,813    12556174496306564471    23 Jun 2013    63.4450
TF    M3,962,759    9261589965653852479    24 Jun 2013    63.0060
TF    M3,964,801    9664758239092017583    25 Jun 2013    63.0674
TF    M3,977,867    9333734548426688497    4 Jul 2013    63.0172
TF    M3,984,611    9727264321022045023    9 Jul 2013    63.0767
TF    M3,987,943    15865097197661369353    11 Jul 2013    63.7825
TF    M3,993,229    15697820045761779689    15 Jul 2013    63.7672
TF    M3,996,281    16232132088556504873    16 Jul 2013    63.8155
TF    M4,002,727    15869623269597059671    19 Jul 2013    63.7829
TF    M4,010,143    11458024374840134951    24 Jul 2013    63.3130
TF    M4,014,767    13876869518095649927    27 Jul 2013    63.5893
TF    M4,019,083    13905515972585089847    30 Jul 2013    63.5923
TF    M4,023,749    13310358497560331287    3 Aug 2013    63.5292
TF    M4,036,391    11119405417589098039    9 Aug 2013    63.2697
TF    M4,048,481    17741041830373275551    15 Aug 2013    63.9437
TF    M4,051,057    16801786620416341871    16 Aug 2013    63.8652
TF    M4,060,663    15346636721256778151    20 Aug 2013    63.7346
TF    M4,065,203    18383033151647681551    21 Aug 2013    63.9950
TF    M4,066,597    16230472112019316703    21 Aug 2013    63.8153
TF    M4,067,831    11349032901921126673    22 Aug 2013    63.2992

It's definitely welcome here, and so is your effort on these (or any) exponents! The more factors the better, and these are "premium" assignments (can't run mfaktc 0.20 on them, making them pure CPU)

LaurV · 2013-08-23, 03:20

Full of envy

, and channeling my inner RDS: if that was CPU work, then it is a big CPU resources waste... Except if they were done on very (but I mean VERY) old hardware that can't do LL nor DC and neither it has enough RAM to do P-1. Which I don't believe, given the (very) short time it took, two months for 2k assignments, at such low exponent, "mid to top" range CPU was used. Or more small machines, but with just a cheap stick of RAM (novadays) you can use that old hardware more efficient (doing P-1 or factoring aliquots).

From the time spent, you may have a mid-top-range GPU and you used normal mfaktc/o, in which case I congratulate you! (@clocker: please be advised that those are exponents over 1 million, therefore in the range of normal mfaktX programs).

OTOH, if you like to do quite low-expo assignments, you can ask Oliver for the "bcp" version, which can TF expos from 2k to 1M (most of them at 61-62 bits right now). Actually, that would also be a a waste, due to the huge amount of ECM done to such exponents, theoretically they won't have any factors below 150 bits or so (50 decimal digits).

c10ck3r · 2013-08-23, 03:41

Quote:

Originally Posted by LaurV

From the time spent, you may have a mid-range GPU and you used normal mfaktc/o, in which case I congratulate you! (@clocker: please be advised that those are exponents over 1 million, therefore in the range of normal mfaktX programs).

OTOH, if you like to do quite low-expo assignments, you can ask Oliver for the "bcp" version, which can TF expos from 2k to 1M (most of them at 61-62 bits right now). Actually, that would also be a a waste, due to the huge amount of ECM done to such exponents, theoretically they won't have any factors below 150 bits or so (50 decimal digits).

Sorry, I should have been more clear. They can't harness the major boost of GPU sieving is what I should have said. 24 GHD/Day on these vs. 146 GHD/Day for more aptly suited assignments on my 460.

2013-08-23, 03:20	#780
LaurV Romulan Interpreter Jun 2011 Thailand 3²·29·37 Posts	Full of envy , and channeling my inner RDS: if that was CPU work, then it is a big CPU resources waste... Except if they were done on very (but I mean VERY) old hardware that can't do LL nor DC and neither it has enough RAM to do P-1. Which I don't believe, given the (very) short time it took, two months for 2k assignments, at such low exponent, "mid to top" range CPU was used. Or more small machines, but with just a cheap stick of RAM (novadays) you can use that old hardware more efficient (doing P-1 or factoring aliquots). From the time spent, you may have a mid-top-range GPU and you used normal mfaktc/o, in which case I congratulate you! (@clocker: please be advised that those are exponents over 1 million, therefore in the range of normal mfaktX programs). OTOH, if you like to do quite low-expo assignments, you can ask Oliver for the "bcp" version, which can TF expos from 2k to 1M (most of them at 61-62 bits right now). Actually, that would also be a a waste, due to the huge amount of ECM done to such exponents, theoretically they won't have any factors below 150 bits or so (50 decimal digits). Last fiddled with by LaurV on 2013-08-23 at 03:22

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
A new factor of F11?!	siegert81	FermatSearch	2	2018-01-24 04:35
A fond farewell	rogue	Lounge	10	2008-11-21 05:25
who can factor 10^100+27?	aaa120	Factoring	17	2008-11-13 19:23
New factor	fivemack	ElevenSmooth	4	2008-05-07 19:28
Shortest time to complete a 2^67 trial factor (no factor)	dsouza123	Software	12	2003-08-21 18:38

2013-08-07, 04:02	#772
Jwb52z Sep 2002 17·47 Posts	P-1 found a factor in stage #1, B1=755000. UID: Jwb52z/Clay, M69601027 has a factor: 1404142018250675959530553 80.216 bits.

2013-08-07, 21:29	#773
Jwb52z Sep 2002 1437₈ Posts	P-1 found a factor in stage #2, B1=725000, B2=16131250. UID: Jwb52z/Clay, M67001843 has a factor: 3233475844526407689088897 81.419 bits.

2013-08-12, 05:58	#774
cheesehead "Richard B. Woods" Aug 2002 Wisconsin USA 1E0C₁₆ Posts	M13121657 has a factor: 45685540395703619321 k = 2² × 5 × 7 × 13 × 956508209

2013-08-13, 16:13	#775
Jwb52z Sep 2002 17·47 Posts	P-1 found a factor in stage #2, B1=725000, B2=16131250. UID: Jwb52z/Clay, M67029509 has a factor: 5347973969691118904158777 82.145 bits.

2013-08-15, 23:32	#776
Uncwilly 6809 > 6502 """"""""""""""""""" Aug 2003 101×103 Posts 23135₈ Posts	332312179 has a factor of 14210518201851118532927. I ran it from 61 to 64 one day in 2009, came back months later, ran it to 66, a month after that ran it to 67, months after that, took it to 70. After some other folks touched it over the years, I worked on it again and found the factor at 73.6 bits.

2013-08-21, 13:39	#777
Jwb52z Sep 2002 799₁₀ Posts	P-1 found a factor in stage #1, B1=725000. UID: Jwb52z/Clay, M67058449 has a factor: 12003053851265177348924609 83.312 bits. P-1 found a factor in stage #1, B1=550000. UID: Jwb52z/Clay, M62826059 has a factor: 6971119617292915006902751 82.528 bits.