![]() |
|
|
#199 | |
|
Jun 2003
7×167 Posts |
Quote:
Obviously the amount and speed of memory will account for a great deal of the difference between different machines. |
|
|
|
|
|
|
#200 | |
|
Jun 2003
7·167 Posts |
Quote:
On the other hand TF is well advanced, so if you do this kind of work, you'll just advance it further without relieving other systems of work they're not well suited to, or finding factors they would miss. |
|
|
|
|
|
|
#201 | |
|
"James Heinrich"
May 2004
ex-Northern Ontario
11·311 Posts |
Quote:
http://mersenne-aries.sili.net/throu...essor&mhz=1100 TF (up to 2^63) on the PentiumIII is vastly superior to FFT performance (by 4x-10x). TF >= 2^64 isn't particularly efficient either, so at that point P-1 would probably be (currently) more GIMPS-beneficial. Note: I'm not sure if my calculator is flawed, or if PrimeNet is really giving an abnormally-large amount of credit for TF compared to FFT... (updates in my calculator thread, when I have any). |
|
|
|
|
|
|
#202 | |
|
"Richard B. Woods"
Aug 2002
Wisconsin USA
11110000011002 Posts |
Quote:
Last fiddled with by cheesehead on 2009-04-26 at 13:59 |
|
|
|
|
|
|
#203 | |
|
"Richard B. Woods"
Aug 2002
Wisconsin USA
22×3×641 Posts |
Quote:
ERROR: Could not find benchmark data for "Intel(R) Pentium(R) III processor" when it spoke to me just now after I clicked on your link. When I manually selected "Intel Pentium III" or "Intel(R) Pentium(R) III processor" (what's the difference?), it worked fine, though. Wait! I see the difference: the single benchmark available for "Intel Pentium III" results in FFT throughput % Eff. of 94.4 to 100 (but no info on TF). whereas the 4 benchmarks for "Intel(R) Pentium(R) III processor" result in miserably-red-backed FFT % Eff. of only 8.8 to 14.4 but cheerily-green (I think) % Eff. of 99.7 to 100 for TF at 2^61 or below. See? That's the Genuine "Intel(R)" difference. Wow! Last fiddled with by cheesehead on 2009-04-26 at 14:21 |
|
|
|
|
|
|
#204 |
|
A Sunny Moo
Aug 2007
USA (GMT-5)
141518 Posts |
|
|
|
|
|
|
#205 |
|
"James Heinrich"
May 2004
ex-Northern Ontario
11·311 Posts |
Sorry, I changed the CPU links to include L2/L3 cache data (to differentiate same-named CPUs with different amounts of cache). And I can't edit my posts anymore to change the links to point to the correct CPU
This is the updated link:http://mersenne-aries.sili.net/throu...|256|0&mhz=800 And yes, some of my (especially older) data has FFT benchmarks only, no TF, so having nothing to compare it to it shows the relative performance of the various FFT sizes (which are all reasonably close to each other), but once you throw TF in the mix the TF numbers are very much higher (still trying to figure if this is my bug or a PrimeNet weirdness) so the FFT-based work looks like a generally bad idea. |
|
|
|
|
|
#206 |
|
Aug 2002
Termonfeckin, IE
22·691 Posts |
I don't think your benchmarks are wrong. PIII really is that much better at factoring under 63 bits. I get similar results with my Athlon.
|
|
|
|
|
|
#207 | |
|
Aug 2002
Ann Arbor, MI
433 Posts |
Quote:
|
|
|
|
|
|
|
#208 | ||
|
"James Heinrich"
May 2004
ex-Northern Ontario
342110 Posts |
Quote:
Quote:
* TF <= 2^62: Core2Duo @ 600MHz * TF >= 2^64: Core2Duo @ 225MHz * FFT (any size): Core2Duo @ 200MHz So, since it's a matter of triple the throughput TF to 2^63 (or less) is most desirable. If you're doing TF on 2^64 or higher, you may as well be doing P-1, the both (approximately) equally (in)efficient in terms of relative performance. |
||
|
|
|
|
|
#209 |
|
Aug 2002
Ann Arbor, MI
1101100012 Posts |
Thanks, those are the kind of numbers I was looking for. Even in LMH ranges, everything has been done to 2^63 (except for 90-91M, which is in progress), and I wasn't going to bother with that anyways. I'll keep it on P-1 unless the memory usage impedes system performance, or it turns out the tests take a lot longer than they should.
|
|
|
|