![]() |
|
|
#1662 |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
100110001101102 Posts |
|
|
|
|
|
|
#1663 |
|
Banned
"Luigi"
Aug 2002
Team Italia
61·79 Posts |
|
|
|
|
|
|
#1664 |
|
"Bill Staffen"
Jan 2013
Pittsburgh, PA, USA
23×53 Posts |
While I've been contributing to prime95 for more years than I can remember, I've been mostly oblivious about what numbers are assigned to me or where the current wavefront is or if potential ll numbers have been sufficiently pre-factored.
While I still run first time LL tests on my cpus, I've been trying lately to do trial factoring on my GPU. I was getting them straight from prime95 until I realised that being a part of GPU to 72 didn't mean joining a prime95 team, per se. Since then (the other day) I've been getting my numbers from them. Still, I'm having trouble working out where the work most needs done. I queued up a week or so of TF'ing 60m range primes to 73, but despite using the visualization tool I'm having a hard time following exactly where the wavefront is, and if I should be factoring a larger set to 71, then 72, then maybe 73 rather than factoring a number up to 73 then moving on to the next. Also it seems like new 100m digit primes (the next prize) aren't being factored in the gpu to 72 project, or if they are I can't parse it out. Basicly I'm looking for help interpreting the relevant graphs on where the ll wavefront is, how fast it's moving, and where the TF wavefront is and how fast it's moving. I suspect there may be multiple LL wavefronts, one in the 60m range (?) and one in the 100m range. Last fiddled with by Aramis Wyler on 2013-01-10 at 22:57 |
|
|
|
|
|
#1665 | |||
|
If I May
"Chris Halsall"
Sep 2002
Barbados
2·67·73 Posts |
Quote:
Quote:
Quote:
(Yes, the next prize is in the 332M range, but very few people expend the months or years required to do a single LL test up there -- our goal is to find the next biggest known prime, not to win money.) Last fiddled with by chalsall on 2013-01-10 at 23:49 Reason: Zooming out the charts probably is more informative. |
|||
|
|
|
|
|
#1666 |
|
"Bill Staffen"
Jan 2013
Pittsburgh, PA, USA
23×53 Posts |
Thank you very much!
|
|
|
|
|
|
#1667 | |
|
P90 years forever!
Aug 2002
Yeehaw, FL
2·32·419 Posts |
Quote:
Ideally, all 60M exponents will be TF'ed to at least 2^73 by a GPU. GPU72 will make sure this happens. If you only TF to 2^71, then GPU72 will reassign the number to someone else to take it the rest of the way. Either way (doing it in stages or all at once), the work is needed and will get done. If I were you, I'd either a) go straight to 2^73 to reduce the headache of getting assignments and reporting results, or b) only go to the next bit level to maximize the "thrill" of finding more factors per unit of GPU time. Your personal preferences will dictate your choice. The 100M exponents are mostly for the fool-hearty. I'd only TF a 100M exponent if requested by a user with a respected reputation. |
|
|
|
|
|
|
#1668 | |
|
6809 > 6502
"""""""""""""""""""
Aug 2003
101×103 Posts
2×7×19×37 Posts |
Quote:
![]() I think that the running of LL's on 100M exponents is not wise ATM. I am trying to make sure that those that do start them, have numbers that have had enough TF on them to make sure that they are not squandering their effort (when it could have been factored reasonably.) |
|
|
|
|
|
|
#1669 |
|
"GIMFS"
Sep 2002
Oeiras, Portugal
27028 Posts |
GPUto72 has just found the 10000th factor!
Congrats to all involved. |
|
|
|
|
|
#1670 |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
978210 Posts |
Just putting this out there for discussion...
A user e-mailed me asking why we're not taking DCTF to 77 instead of 70. I pointed them to James' analysis and (hopefully) explained that even with the new GPU seiving it would only make sense to go to 71 in the current range we're working. And, also, that the LLTF work is really the most important at the moment. However, it raises the question: for those who are doing DCTF work (where we're currently over 500 days ahead of the wave), should we bump the release level to 71, and perhaps bring back in some candidates in the 30M, 31M and 32M regions to go from 70 to 71? While I personally don't think this is the best thing for GIMPS, I also think that people should be able to do what they want to do. Is this wanted by anyone? If so, I'd suggest we simply increase the current release level for DCTF, and bring in a few candidates at a time at the top of 30M for processing, and work down until we meet the wavefront, Then start working upwards from 31M. Thoughts? |
|
|
|
|
|
#1671 |
|
P90 years forever!
Aug 2002
Yeehaw, FL
2·32·419 Posts |
No. James' table improperly estimates the DCTF crossover. Since these exponents have already had P-1 done, TF to 2^71 will find fewer factors than LLTF. James should be able to compute a "proper" crossover based on finding approximately 1 factor per 100 DCTF exponents (GPU72 should be able refine this approximation by calculating how many factors are being found DCTFing to 2^70).
|
|
|
|
|
|
#1672 | |
|
If I May
"Chris Halsall"
Sep 2002
Barbados
2×67×73 Posts |
Quote:
|
|
|
|
|
![]() |
| Thread Tools | |
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 |