GPU to 72 status... - Page 220

chalsall · 2013-09-24, 18:38

Quote:

Originally Posted by davieddy

By 90M it might be time to go to 75 bits.

Welcome back David...

We missed you....

kracker · 2013-09-24, 18:57

chalsall · 2013-09-24, 19:52

Quote:

Originally Posted by kracker

bs meter

My apologies for this, but I was taught that you should put on your life vest before you put on your boots. And then before you left shore.

Perhaps I was instructed incorrectly...

kracker · 2013-09-24, 21:17

Quote:

Originally Posted by chalsall

My apologies for this, but I was taught that you should put on your life vest before you put on your boots. And then before you left shore.

Perhaps I was instructed incorrectly...

WHAT? WHO CAAARES?

BOOTS FIRST

kladner · 2013-09-24, 21:30

Hi, David.

Plus ça change, plus c'est la même chose.

TheMawn · 2013-09-25, 04:34

Welcome back, David.

Any kids on your lawn, lately?

c10ck3r · 2013-09-25, 16:01

I think David actually has a valid point. It seems that a breadth-first TF regimen in the upcoming ranges would be preferable to a slowly progressing full depth wave, or at least in addition to the current wavefront style. Might there be interest in doing a breadth-based TF project to take, say, everything from 80M-100M to 69 bits (or 70, even)? We know factors are cheaper at lower bit depths, so why not take advantage of that? I reckon there should be over 44000 factors to take 80M-100M up to the same bit depth as the 50M region, at (just over) half the cost.

LaurV · 2013-09-25, 16:16

Don't like what GPU72 is doing? Anybody is welcomed to take her own exponent from PrimeNet, do TF how deep she likes it, do P-1, then do LL.

chalsall · 2013-09-25, 16:27

Quote:

Originally Posted by c10ck3r

I think David actually has a valid point.

I respectfully disagree. Although I'm happy to debate the issue (again) and be convinced otherwise (so long as the discussion is rational rather than hysterical...).

The stated agenda of GPU to 72 73 74 is to help find the next Mersenne Prime as quickly as possible.

The best way to do this, in my opinion, is to TF as deeply as Makes Sense according to James' analysis of the cross over point, balanced with our available firepower.

This report shows that we can TF everything up to 67M to 74 "bits" in 229 days, while it's going to take PrimeNet 576 days to LL to that range. Note that we actually don't hold every candidate not yet TFed to 74 -- this report shows that it's going to take us 186 days to TF what we actually "own". Note that these reports are updated five times an hour.

Now, if some wanted to do TFing in the 80M to 100M range, I could facilitate that. However, I would argue that work is better left to those CPUs which are still configured to do TFing, and which George is continuing to coordinate.

(Rational) thoughts?

kladner · 2013-09-25, 16:36

Not all of the GPU72 TF progress is taking place in 62-63M, 73 to 74 bits. I roughly alternate those with lowest available exponent taken from 71 to 74 bits, along with any lower-factored strays that show up.

Somewhere in there I have gotten my Factors-Predicted-vs-Found gap down from around 8, to 2.6 ATM.

lycorn · 2013-09-25, 20:46

Quote:

Originally Posted by sonjohan

I shut it down for a long time because I noticed that the fans started to make too much noise.
With a lower temp, they activate less frequently and I can live with the noise it makes now.

How old is your GPU?
That increased amount of noise, together with rising temperatures, may indicate some fan overhaul is needed. You may wish to check whether the fans need to be lubricated. Check the fan rpm, if you have the means, that is a good indicator.
I´ve just done that to my GTX560 with success (fan rotation back to normal speed, less noise, and the temperature 15-20 ºC lower).

2013-09-25, 16:16	#2417
LaurV Romulan Interpreter Jun 2011 Thailand 2×3×1,609 Posts	Don't like what GPU72 is doing? Anybody is welcomed to take her own exponent from PrimeNet, do TF how deep she likes it, do P-1, then do LL. Last fiddled with by LaurV on 2013-09-25 at 16:17

2013-09-25, 16:36	#2419
kladner "Kieren" Jul 2011 In My Own Galaxy! 2×3×1,693 Posts	Not all of the GPU72 TF progress is taking place in 62-63M, 73 to 74 bits. I roughly alternate those with lowest available exponent taken from 71 to 74 bits, along with any lower-factored strays that show up. Somewhere in there I have gotten my Factors-Predicted-vs-Found gap down from around 8, to 2.6 ATM. Last fiddled with by kladner on 2013-09-25 at 16:38

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-09-24, 18:57	#2411
kracker "Mr. Meeseeks" Jan 2012 California, USA 878₁₆ Posts

2013-09-24, 21:30	#2414
kladner "Kieren" Jul 2011 In My Own Galaxy! 10158₁₀ Posts	Hi, David. Plus ça change, plus c'est la même chose.

2013-09-25, 04:34	#2415
TheMawn May 2013 East. Always East. 3277₈ Posts	Welcome back, David. Any kids on your lawn, lately?

2013-09-25, 16:01	#2416
c10ck3r Aug 2010 Kansas 223₁₆ Posts	I think David actually has a valid point. It seems that a breadth-first TF regimen in the upcoming ranges would be preferable to a slowly progressing full depth wave, or at least in addition to the current wavefront style. Might there be interest in doing a breadth-based TF project to take, say, everything from 80M-100M to 69 bits (or 70, even)? We know factors are cheaper at lower bit depths, so why not take advantage of that? I reckon there should be over 44000 factors to take 80M-100M up to the same bit depth as the 50M region, at (just over) half the cost.