GPU to 72 status... - Page 397

storm5510 · 2019-11-02, 12:36

Quote:

Originally Posted by chalsall

Yup, that's how this thing works...

Not clear what you mean by ceiling value. We "release" back to Primenet at 77 (currently).

Sorry, I should have written end bits.

Sometime during the night, I crossed over into 96M, still running to 74 bits. I may have mentioned this before. It takes about 30 minutes for each of these with mfaktc. 2⁷⁷ would take four hours each so I would not get many done.

I do not run my 1080 at full capacity. The reason being is that, if any were to happen to it, I would never be able to replace it. When I bought it, I was still working. I am retired now. I use Afterburner to throttle it back. I have the power limit set at 80%. At that level, it still runs over 1,000 GHz-d/day. That's good enough, for me, anyway.

chalsall · 2019-11-02, 23:33

Quote:

Originally Posted by storm5510

Sometime during the night, I crossed over into 96M, still running to 74 bits. I may have mentioned this before. It takes about 30 minutes for each of these with mfaktc. 2⁷⁷ would take four hours each so I would not get many done.

Yup. A 76 -> 77 bit run takes ten hours and something on a K80, and 3:40 on a P100.

But /someone/ has to do them (hint-hint... LG72D Luke)...

Just to reminisce a bit... When we all started this adventure way back in 2011, we had no idea where we should actually TF to. GPU72 was named as it was because it rhymed, not because we actually thought we would actually regularly get to that level.

A huge shout-out to James, and his economic cross-over analysis which shows exactly where it "makes sense" to TF to, vs. where there will be more throughput by just running a CUDA-based LL job.

Which brings something up... We're going to have to start planning on going up to 78 soon...

PhilF · 2019-11-03, 00:03

If we take the future into consideration now, we should rename the effort to GPU92.

Uncwilly · 2019-11-03, 00:18

Quote:

Originally Posted by PhilF

If we take the future into consideration now, we should rename the effort to GPU92.

GPU95 sounds better to me.

petrw1 · 2019-11-03, 00:45

Quote:

Originally Posted by chalsall

A huge shout-out to James, and his economic cross-over analysis which shows exactly where it "makes sense" to TF to, vs. where there will be more throughput by just running a CUDA-based LL job.

Which brings something up... We're going to have to start planning on going up to 78 soon...

Your link is for the 2080Ti; still a top-end fringe card.
Shouldn't we be using a more mainstream (common) card like the 1080Ti.?

chalsall · 2019-11-03, 01:02

Quote:

Originally Posted by petrw1

Your link is for the 2080Ti; still a top-end fringe card. Shouldn't we be using a more mainstream (common) card like the 1080Ti.?

It depends on what is "in the fleet", and the total GHzD/D available. Even for a 1080 (CC 6.1) it makes sense to go to 78 at 115M or so.

Also, some just like finding factors. And so will do a "bit or two" past the "optimal cross-over" point.

axn · 2019-11-03, 04:12

Quote:

Originally Posted by petrw1

Your link is for the 2080Ti; still a top-end fringe card.
Shouldn't we be using a more mainstream (common) card like the 1080Ti.?

You should be using an even more mainstream card like 1660 Ti which beats the crap out of 1080 Ti in TF at fraction of the cost and power consumption. Since it is the same family as 2080 Ti, the conclusion remains unchanged.

storm5510 · 2019-11-03, 14:00

Quote:

Originally Posted by chalsall

Yup. A 76 -> 77 bit run takes ten hours and something on a K80, and 3:40 on a P100.

But /someone/ has to do them (hint-hint... LG72D Luke)...

Just to reminisce a bit... When we all started this adventure way back in 2011, we had no idea where we should actually TF to. GPU72 was named as it was because it rhymed, not because we actually thought we would actually regularly get to that level.

A huge shout-out to James, and his economic cross-over analysis which shows exactly where it "makes sense" to TF to, vs. where there will be more throughput by just running a CUDA-based LL job.

Which brings something up... We're going to have to start planning on going up to 78 soon...

2⁷⁸ It may be a good idea, but it would not be practical, at least for me. Someone having a 16xx or 20xx series card would be better suited to do this work. Those of us with less powerful GPU's can still do the lower bit tests. As for me, 75 bits would be my absolute ceiling.

Off-topic: My son is a big AMD fan. He recently built a new system. There was a compatibility issue with AMD video cards. He ended up with a GTX-1660. He doesn't understand it, nor does he like it. He'll go back to AMD sometime. I'll see if I can get my hands on his 1660 when he does.

chalsall · 2019-11-03, 14:34

Quote:

Originally Posted by storm5510

Someone having a 16xx or 20xx series card would be better suited to do this work. Those of us with less powerful GPU's can still do the lower bit tests. As for me, 75 bits would be my absolute ceiling.

And that is exactly why people are allowed to set their own "Pledge" level (and even range, if they so choose).

Whatever rocks your boat! Every "bit" helps!

Quote:

Originally Posted by storm5510

Off-topic: My son is a big AMD fan. He recently built a new system. There was a compatibility issue with AMD video cards. He ended up with a GTX-1660. He doesn't understand it, nor does he like it. He'll go back to AMD sometime. I'll see if I can get my hands on his 1660 when he does.

Yeah; I can relate...

I always like to support the "underdog" wherever possible. A while ago I was building a new Linux workstation; I bought a cheap AMD GPU card to drive a monitor. All kinds of compatibility issues -- and this was with CentOS; pretty mainstream distribution.

At the end of the day, I took the card back, and instead got an NVidia card. And this wasn't even for compute; just to drive a display.

Sometimes you just have to choose the option which just works, and get on with the job.

PhilF · 2019-11-03, 15:13

Quote:

Originally Posted by storm5510

Off-topic: My son is a big AMD fan. He recently built a new system. There was a compatibility issue with AMD video cards. He ended up with a GTX-1660. He doesn't understand it, nor does he like it. He'll go back to AMD sometime. I'll see if I can get my hands on his 1660 when he does.

I have been a computer professional since the 1970's, and AMD has had that problem for this entire time. They simply cannot write drivers, period. I would never consciously use an AMD video card for my main system, no matter if it was linux or Windows.

Now, if someone just gave me a Radeon VII, I would use it to crunch numbers in a separate box, but that's about it.

Just my 2 cents worth.

chalsall · 2019-11-03, 17:21

Quote:

Originally Posted by PhilF

If we take the future into consideration now, we should rename the effort to GPU92.

LOL...

Domain registered...

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

2019-11-03, 00:03	#4359
PhilF Feb 2005 Colorado 5×131 Posts	If we take the future into consideration now, we should rename the effort to GPU92.