On Wednesday 10 July 2002 22:38, Gerry Snyder wrote: > I am puzzled. I am running two copies of prime95 (one with no options, > one with -A1) on a dual 1 GHz P3 computer under Windows 2K. One is > factoring, and the other is doing an LL test of an exponent in the > 15,xxx,xxx range. The torture test was run for several hours with no > problems. W2K recognizes the two CPU's and the task manager shows each > mprime getting 50% of the total CPU time and almost no idle time. > > The only problem is a galloping completion date. After about 11 days of > execution (split among several reboot sessions), with some time spent in > trial factoring and P-1 factoring, the LL is over 26% complete. The > per-iteration of .191 seconds indicates a total LL time of around 33 > days. Right after I start it running, the completion date is reasonable. > But every few hours it contacts the PrimeNet Server to extend the > completion date by weeks. The "Status" now menu shows completion in > April 2003 (this execution has been for about 5 days). > > Any idea what could be the problem?
Did you change the CPU type/speed - perhaps after importing local.ini from a different system? Keep a track of the changing value of RollingAverage in local.ini; if it's a long way different from 1000 (say outside the range 500-1500) try stopping Prime95, editing RollingAverage to 1000 & restarting. There have been problems with some versions of Prime95/mprime where the CPU type would be detected wrongly. Suggest changing to v22.1 (or v22.5) as v22 has much better CPU type/speed detection code - automatic, too, so you can't mis-set it :-) BTW my dual 1 GHz PIII system, with a similar work loading to yours, has RollingAverage=1128 on the CPU running LL tests. Regards Brian Beesley _________________________________________________________________________ Unsubscribe & list info -- http://www.ndatech.com/mersenne/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers