GPU to 72 status...

[TheMawn]

Originally Posted by chalsall

bring GPU72's functionality back into Primenet.

[chalsall]

Originally Posted by flashjh

Just to clarify... GPU72 isn't going away; the "pretty graphs" will stay and assignments will still be available through it. But instead of GPU72 researving hundreds of thousands of candidates, it will instead be a proxy for Primenet, much like how LL and DC assignments now work.

[flashjh]

I'm just giving you a hard time :-)

I'm sure everyone here understands!

[petrw1]

Originally Posted by chalsall

Just to clarify... GPU72 isn't going away; the "pretty graphs" will stay and assignments will still be available through it. .

Does "pretty graphs" include what is in mersenne.info?

If no .... such is life.

If yes there is the small issues of 0-1,000,000 and a couple other small ranges missing for the last few months.
And not only are the details missing but the total are also wrong with this data excluded.

[chalsall]

Originally Posted by petrw1

Does "pretty graphs" include what is in mersenne.info?

Yes.

Originally Posted by petrw1

If yes there is the small issues of 0-1,000,000 and a couple other small ranges missing for the last few months. And not only are the details missing but the total are also wrong with this data excluded.

Yeah... (sigh) I know... (sigh)

I might have cycles to fix this next February. It's a "non-trivial problem space", caused by a very stupid programmer....

[chalsall]

Originally Posted by Chuck

I'm going to continue to Let GPU72 Decide

So everyone knows, "LG72D" on the LLTF request form has been brought back into the LL range.

You guys hit this one out of the park!

[James Heinrich]

I'm gonna unreserve the rest of my work since my second GTX670 seems to have gone flaky, won't start mfaktc unless I drop the clock speed from 1100MHz to 700MHz

[petrw1]

Originally Posted by chalsall

So everyone knows, "LG72D" on the LLTF request form has been brought back into the LL range.

You guys hit this one out of the park!

I might suggest two possible options for any excess Horse Power. ... there are many more.

1. Allocate it to DC-TF. As 3M (Mark, Mawn and Me) discussed in posts 3301 - 3304, DC-TF could be a thing of the past within a year leaving only 1 pool of effort to manage making it much simpler.

2. Become GPU to 75 in the LL Range

[Mark Rose]

Originally Posted by petrw1

I might suggest two possible options for any excess Horse Power. ... there are many more.

1. Allocate it to DC-TF. As 3M (Mark, Mawn and Me) discussed in posts 3301 - 3304, DC-TF could be a thing of the past within a year leaving only 1 pool of effort to manage making it much simpler.

2. Become GPU to 75 in the LL Range

Those of use who want to finish all the DCTF could leave our systems set to LG72D DCTF. I will for the time being.

[NickOfTime]

Originally Posted by Mark Rose

Those of use who want to finish all the DCTF could leave our systems set to LG72D DCTF. I will for the time being.

I will be switching my GPU processing back to protein crunching (Poem@ or Folding@) in Jan...) but until then I will leave them on LG72D LLTF .... but you can PM me if there is temporary shortage :-) (Hmm, Pretend I joined a chess team with LaurV )

[lycorn]

Originally Posted by chalsall

Yes.



Yeah... (sigh) I know... (sigh)

I might have cycles to fix this next February. It's a "non-trivial problem space", caused by a very stupid programmer....

Great. That´s good news. I really like the info provided by GIMPS Visualization, and have been a bit disappointed by its lack of reliability over the last few months. Look forward to having it fixed.