At 12:43 PM 5/26/2002 -0400, Jud McCranie wrote: >I've been off the mailing list for a while. I just went from ver 21.4 to >22.3 and the calculation of time per iteration seems to be off. I'm >running a 15,000,000 exponent on a 1.3 GHz Athlon. It shows (what would >be) a remarkable 0.037 sec per iteration, but it takes about 13 minutes >for 6000 iterations, which is actually 0.13 sec/iter, 3.5 times as >much. The expected completion dates under Status look right. >Is there a bug in the per iteration calculation in ver 22.3?
Sure looks like a bug. One of the changes in version 22 is the use of the Windows QueryPerformanceCounter system call rather than RDTSC to time each iteration. Another change is that prime95 automatically deduces your CPU speed and type. Please email me your prime.ini and local.ini files and the output of the Options/CPU dialog box (hint - you can do Options/Benchmark and the cpu information will be written to results.txt). I'm also interested in hearing from any other users that find version 22.3 is not detecting their CPU type and speed properly. _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
