GPU to 72 status... - Page 161

chalsall · 2013-01-26, 01:11

Quote:

Originally Posted by kracker

Sure! Although my firepower sucks, Count me in

OK, thanks guys.

I have started bringing in candidates. Only a thousand at a time until we've got a comfortable margin.

Go to the DC TF Assignment form, set the "Will factor to" field to be 70, and the "Option" to be "Lowest Exponent".

I would suggest that people try to only take a hundred or so at a time, and try to return results at least every hour or so, at least at the start of this exercise.

kracker · 2013-01-26, 01:29

Quote:

Originally Posted by chalsall

OK, thanks guys.

I have started bringing in candidates. Only a thousand at a time until we've got a comfortable margin.

Go to the DC TF Assignment form, set the "Will factor to" field to be 70, and the "Option" to be "Lowest Exponent".

I would suggest that people try to only take a hundred or so at a time, and try to return results at least every hour or so, at least at the start of this exercise.

Thanks

swl551 · 2013-01-26, 02:57

Quote:

Originally Posted by chalsall

OK, thanks guys.

I have started bringing in candidates. Only a thousand at a time until we've got a comfortable margin.

Go to the DC TF Assignment form, set the "Will factor to" field to be 70, and the "Option" to be "Lowest Exponent".

I would suggest that people try to only take a hundred or so at a time, and try to return results at least every hour or so, at least at the start of this exercise.

This work can be fetched via the GPU72WorkFetcher utility by setting the URL in the config file to
URL:https://www.gpu72.com/account/getassignments/dctf/

(set the pledge and option as Chris has stated)

LaurV · 2013-01-26, 04:38

I will join with one gtx580, for a week or so, starting tonight (my time) to help setting this debate once forever

chalsall · 2013-01-26, 04:47

Quote:

Originally Posted by LaurV

I will join with one gtx580, for a week or so, starting tonight (my time) to help setting this debate once forever

Coolness. Thanks.

firejuggler · 2013-01-26, 05:18

took 30 expo for 69-70.... just enough for the night (GTI 560 normal) around 26 minutes for a 31075xxx exponent (3.85GhzD)

James Heinrich · 2013-01-26, 13:06

Quote:

Originally Posted by henryzz

Adding to the confusion doesn't James' page still rely on data from mfaktc 1.19 not 1.20. Isn't the new version quite a bit more efficient as it allows the cpu to be used for DC/LL.

My GPU TF-LL comparison page is purely GPU crossover points, although you are correct that GPU-sieving does allow the CPU to be used for other tasks. But the performance numbers reflect mfaktc v0.20 performance (as does the GPU-TF expected performance page).

Quote:

Originally Posted by Prime95

It would be great if James could change the chart to show the DC breakeven point when P-1 has been performed (the factoring chart LaurV pointed to, http://www.gpu72.com/reports/factoring_cost/, gives enough information to produce a fairly accurate adjustment to the chance of finding a factor). For extra credit, the web page could offer a checkbox to show the crossover points assuming no P-1 done.

I'll see what I can come up with over the next few days.

Mini-Geek · 2013-01-26, 14:55

Quote:

Originally Posted by chalsall

... but I'm going to run a few hundred TF runs immediately in front of the wave front in 31M to 70 so we can get a reasonable idea as to what type of percentage we might expect. (31M to 70 has only had 83 attempts before, with zero factors found, so we don't actually have any useful data on what we might expect exactly there.)

http://www.mersenne.org/various/math.php says:

Quote:

the chance of finding a factor between 2^X and 2^X+1 is about 1/x

So, assuming all exponents are already at 69 and being brought to 70, we should expect 1/69, or 1.45%, to have factors, right? Edit: I think I just realized why it's not that simple: P-1 factoring will find a portion of the factors. Since not every exponent was P-1'd to the same extent, this becomes much harder to calculate over the range, and to get an accurate figure without simply testing and looking at results, you'd have to get all complete P-1 bounds and calculate based on that.

Prime95 · 2013-01-26, 15:13

Quote:

Originally Posted by Mini-Geek

Since not every exponent was P-1'd to the same extent, this becomes much harder to calculate over the range...

All true, but we aren't seeking perfection here. I'd say if we know our chance of finding a factor within 10%, that's good enough to determine a very reasonable DCTF crossover point.

Using chasall's 1.1546% number we get 1 chance in 86.6 of finding a factor. James knows how to turn that into crossover points.

kracker · 2013-01-26, 16:23

Just started... it is doing one every 40 min, about ~200M/s on mfakto, 7770.

Chuck · 2013-01-26, 16:42

Took 100 last night; I'm doing one every 12 minutes.

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-26, 04:38	#1764
LaurV Romulan Interpreter Jun 2011 Thailand 2⁶×151 Posts	I will join with one gtx580, for a week or so, starting tonight (my time) to help setting this debate once forever

2013-01-26, 05:18	#1766
firejuggler Apr 2010 Over the rainbow 2×1,303 Posts	took 30 expo for 69-70.... just enough for the night (GTI 560 normal) around 26 minutes for a 31075xxx exponent (3.85GhzD)

2013-01-26, 16:23	#1770
kracker "Mr. Meeseeks" Jan 2012 California, USA 2³×271 Posts	Just started... it is doing one every 40 min, about ~200M/s on mfakto, 7770.

2013-01-26, 16:42	#1771
Chuck May 2011 Orange Park, FL 1565₈ Posts	Took 100 last night; I'm doing one every 12 minutes.