GPU to 72 status... - Page 163

swl551 · 2013-01-27, 01:04

M31080983 has a factor: 787976240107172165047 [TF:69:70:mfaktc 0.20 barrett76_mul32_gs]

chalsall · 2013-01-27, 01:28

Quote:

Originally Posted by chalsall

Sorry -- doing a complete back-up in preparation of a potential big announcement. It will be back shortly....

Sorry everyone. That took longer than expected...

She's back.

petrw1 · 2013-01-27, 02:12

Quote:

Originally Posted by chalsall

...a potential big announcement....

Your's or George's?

swl551 · 2013-01-27, 02:16

Quote:

Originally Posted by petrw1

Your's or George's?

Let me guess.. GPU72 is with child? GPU73?

chalsall · 2013-01-27, 02:18

Quote:

Originally Posted by petrw1

Your's or George's?

George's.

The "SlashDot Effect" can bring unwanted attention....

Aramis Wyler · 2013-01-27, 02:37

I pulled 200 DCs and the 2nd one had a factor:
got assignment: exp=31110319 bit_min=69 bit_max=70 (3.84 GHz-days)
Starting trial factoring M31110319 from 2^69 to 2^70 (3.84 GHz-days)
k_min = 9487138500840
k_max = 18974277003032
Using GPU kernel "barrett76_mul32_gs"
Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
Jan 26 21:34 | 3896 84.4% | 0.845 2m07s | 409.34 69941 n.a.%
M31110319 has a factor: 718932871683122603489
found 1 factor for M31110319 from 2^69 to 2^70 (partially tested) [mfaktc 0.20 barrett76_mul32_gs]
tf(): total time spent: 11m 26.995s

409 ghz days/day at this range. I am not sure why the ghz/day goes up based on the range I'm factoring. Shoudn't the smaller numbers be worth less days if they factor so much more quickly?

bcp19 · 2013-01-27, 04:56

Wow, I missed a big discussion. Since you seem to have the firepower working, I will continue with my 33M to 71 runs. I've had the 'crossover' discussion with Larv too many times already (back when CPUs affected the outcome), but looking at what has been posted, 12 min per = 5 per hour, 20 hour LL = 1 LL per 100 TF. 80-120 TF per LL is considered the 'gray' zone, some feel it is not worth it, some do. The problem here has always come down to, as George pointed out, 'apples and oranges'. Suffice it to say, if some people think it worthwhile, what's wrong with letting them do it?

garo · 2013-01-27, 09:12

bcp19: it is a volunteer project so you are free to do what you want. LLTF is still the most useful for the project as a whole. As davieddy said (and he is right this one time) taking 31M to 70 is like taking 62M to 74 and we are having trouble making sure all 62M will be at 73 let alone 74.

But whatever floats your boat. Everything helps. My observation was simply that 31M to 70 is better than 33M to 71.

swl551 · 2013-01-27, 12:34

Quote:

Originally Posted by swl551

M31080983 has a factor: 787976240107172165047 [TF:69:70:mfaktc 0.20 barrett76_mul32_gs]

Chris, should we continue processing this range or go back to our regular work?

LaurV · 2013-01-27, 13:31

I did my 200, got 3 factors.
That is, I got some profit, having cleared 3 expos in the time I would only clear 2 by DCLL.
I was lucky :D
Not convincing.
I will take 100 more.

VictordeHolland · 2013-01-27, 14:24

I also reserved 100 DC 31M tasks, my 480 and 470 should start working on them in about ~1 hour.

2013-01-27, 01:04	#1783
swl551 Aug 2012 New Hampshire 2³×101 Posts	another factor M31080983 has a factor: 787976240107172165047 [TF:69:70:mfaktc 0.20 barrett76_mul32_gs]

2013-01-27, 02:37	#1788
Aramis Wyler "Bill Staffen" Jan 2013 Pittsburgh, PA, USA 2³·53 Posts	I pulled 200 DCs and the 2nd one had a factor: got assignment: exp=31110319 bit_min=69 bit_max=70 (3.84 GHz-days) Starting trial factoring M31110319 from 2^69 to 2^70 (3.84 GHz-days) k_min = 9487138500840 k_max = 18974277003032 Using GPU kernel "barrett76_mul32_gs" Date Time \| class Pct \| time ETA \| GHz-d/day Sieve Wait Jan 26 21:34 \| 3896 84.4% \| 0.845 2m07s \| 409.34 69941 n.a.% M31110319 has a factor: 718932871683122603489 found 1 factor for M31110319 from 2^69 to 2^70 (partially tested) [mfaktc 0.20 barrett76_mul32_gs] tf(): total time spent: 11m 26.995s 409 ghz days/day at this range. I am not sure why the ghz/day goes up based on the range I'm factoring. Shoudn't the smaller numbers be worth less days if they factor so much more quickly? Last fiddled with by Aramis Wyler on 2013-01-27 at 02:38 Reason: spelling.

2013-01-27, 13:31	#1792
LaurV Romulan Interpreter Jun 2011 Thailand 2⁶×151 Posts	I did my 200, got 3 factors. That is, I got some profit, having cleared 3 expos in the time I would only clear 2 by DCLL. I was lucky :D Not convincing. I will take 100 more. Last fiddled with by LaurV on 2013-01-27 at 13:31

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Status	Primeinator	Operation Billion Digits	5	2011-12-06 02:35
62 bit status	1997rj7	Lone Mersenne Hunters	27	2008-09-29 13:52
OBD Status	Uncwilly	Operation Billion Digits	22	2005-10-25 14:05
1-2M LLR status	paulunderwood	3*2^n-1 Search	2	2005-03-13 17:03
Status of 26.0M - 26.5M	1997rj7	Lone Mersenne Hunters	25	2004-06-18 16:46

2013-01-27, 04:56	#1789
bcp19 Oct 2011 7×97 Posts	Wow, I missed a big discussion. Since you seem to have the firepower working, I will continue with my 33M to 71 runs. I've had the 'crossover' discussion with Larv too many times already (back when CPUs affected the outcome), but looking at what has been posted, 12 min per = 5 per hour, 20 hour LL = 1 LL per 100 TF. 80-120 TF per LL is considered the 'gray' zone, some feel it is not worth it, some do. The problem here has always come down to, as George pointed out, 'apples and oranges'. Suffice it to say, if some people think it worthwhile, what's wrong with letting them do it?

2013-01-27, 09:12	#1790
garo Aug 2002 Termonfeckin, IE 2²·691 Posts	bcp19: it is a volunteer project so you are free to do what you want. LLTF is still the most useful for the project as a whole. As davieddy said (and he is right this one time) taking 31M to 70 is like taking 62M to 74 and we are having trouble making sure all 62M will be at 73 let alone 74. But whatever floats your boat. Everything helps. My observation was simply that 31M to 70 is better than 33M to 71.

2013-01-27, 14:24	#1793
VictordeHolland "Victor de Hollander" Aug 2011 the Netherlands 10010011000₂ Posts	I also reserved 100 DC 31M tasks, my 480 and 470 should start working on them in about ~1 hour.