GPU72 / MISFIT use for 100M digit range?

[LaurV]

Originally Posted by chalsall

...(assuming the "High" field can go past 100,000,000).

Well, indeed there are only 9 positions to fill there, so you can't fill a gig, but it works perfectly for me, with 999999999 (nine of nines, bet you did not think to it! )

(that's to say I am starting to play with misfit, and up to now I am quite happy of this combination misfit+gpu72+332M fetching, it works as advertized! Manual fetching only, no auto fetching yet, waiting for the current work to finish, also no result reported yet, missing a button with "report results now" just to make sure it is working, so I can get the inner peace before going to sleep... :razz:) forget I said that! solved with a scheduled upload, it works well.

Thanks to all involved in developing such a nice toy. Nighty night!

[chalsall]

Originally Posted by LaurV

Well, indeed there are only 9 positions to fill there, so you can't fill a gig, but it works perfectly for me, with 999999999 (nine of nines, bet you did not think to it! )

Please correct me if I'm wrong, but is not 999,999,999 past 100,000,000?

Originally Posted by LaurV

(that's to say I am starting to play with misfit, and up to now I am quite happy of this combination misfit+gpu72+332M fetching, it works as advertized! Manual fetching only, no auto fetching yet, waiting for the current work to finish, also no result reported yet, missing a button with "report results now" just to make sure it is working, so I can get the inner peace before going to sleep... )

Thanks for your cycles.

[LaurV]

Originally Posted by chalsall

Please correct me if I'm wrong, but is not 999,999,999 past 100,000,000?

You did not catch my point: I bet you did not think to it! You tried to fill 1G and it did not work, and you assumed that 100k is the MAX value that can be filled, otherwise your initial remark makes no sense. Do not negate!






(and don't ask me how I know, it is because that I was doing/thinking first, too )

p.s. edited my post above.

[swl551]

Originally Posted by LaurV

...missing a button with "report results now" just to make sure it is working, so I can get the inner peace before going to sleep... )[/STRIKE] forget I said that! solved with a scheduled upload, it works well.

Thanks to all involved in developing such a nice toy. Nighty night!

Button is there.

[LaurV]

Originally Posted by swl551

Button is there.

Grrr, how was I suppose to know? I wanted to "report" results to gimps, not to "export" them (in another file, or whatever) nor to launch some alien tools called i/o manager

Now I know what the button does... Thanks for clarifying.

[chalsall]

Originally Posted by LaurV

You did not catch my point: I bet you did not think to it! You tried to fill 1G and it did not work, and you assumed that 100k is the MAX value that can be filled, otherwise your initial remark makes no sense. Do not negate! .

Sigh...

The GPU72 form was updated to have a high of 1,000,000,000 as soon as we deployed this. The SaaS interface had no limitations.

But, yes, you're very clever. But, at the same time, 334,000,000 in MISFIT would have worked just as well....

[LaurV]

ok, this misfit is also lucky! First factor found after only ~25GHzD of TFLMH: 6666452182880492677553.

Now I will really sleep well...
3:00 AM here.

[swl551]

Originally Posted by LaurV

Grrr, how was I suppose to know? I wanted to "report" results to gimps, not to "export" them (in another file, or whatever) nor to launch some alien tools called i/o manager

Now I know what the button does... Thanks for clarifying.

Long ago it was only an EXPORT.. Button text never changed. the IO manager gives you async processing of results reporting/uploading. It will queue and retry etc show error conditions etc.

[chalsall]

Originally Posted by swl551

Long ago it was only an EXPORT.. Button text never changed. the IO manager gives you async processing of results reporting/uploading. It will queue and retry etc show error conditions etc.

Hey, no real problem.

Still today many have to click on "Start" to "Shutdown", "Reboot", or "Halt"...

[swl551]

Bear with me if I have zero understanding and say all this wrong.....

So far I've been factoring in the 60m range via what GPU72 hands me and I was satisfied. What does jumping to WAY up to 332m do for us that has more/less meaning than working 60m?

My best guess is the folks doing 100M+ LL tests can benefit from this work.


Please enlighten me if you have a moment. (whomever can).

And why would the credits be so low if the exponents are so large?
assignment: exp=332410xxx bit_min=72 bit_max=73 (2.88 GHz-days)

[chalsall]

Originally Posted by swl551

So far I've been factoring in the 60m range via what GPU72 hands me and I was satisfied. What does jumping to WAY up to 332m do for us that has more/less meaning than working 60m?

Work in the 60M ranges is still the most important to the GIMPS effort as a whole. We're here to find large primes.

The 332M range (AKA the 100M digit range) is where the next big prize money is ($150,000 from the EFF). However, it takes ~1 year or so for a high-powered modern computer to complete a single one up there. It doesn't make much sense, but some still do it.

Uncwilly took it upon himself quite some time ago to coordinate TFing efforts up there so those who do LLing work are not wasting as much of their time than they might otherwise do (because factors can be found using TF and P-1 efforts which are far less expensive).