![]() |
![]() |
#1 |
Jan 2009
2×3 Posts |
![]()
Found a couple of threads mentioning the Completion times being off, but none that mention the CPU Speed, which will obviously affect the completion time calculation.
I just upgraded 3 systems from version 24.14 to 25.8 build 5. Version 25.8 is incorrectly reporting the CPU speed, which is affecting Estimated Completion times. (by 7 years on the PIII system) Code:
Processor Version 24.14 Version 25.8 Type Reports Reports Pentium D 3.00 GHz 2992.49 GHz 200 MHz Celeron 1400 MHz 935.47 MHz 449 MHz (underclocked to 933 MHz) PIII 700 784.96 MHz 100 MHz (OC to 785 MHz) Jerry |
![]() |
![]() |
![]() |
#2 |
P90 years forever!
Aug 2002
Yeehaw, FL
2·3,677 Posts |
![]()
What is weird is that the cpu speed detection code did not change between version 25 and version 24.
I'll look at it, but in the meantime look at undoc.txt. There should be a CPUSpeed entry you can use to override the detected speed. |
![]() |
![]() |
![]() |
#3 |
Jan 2009
2×3 Posts |
![]()
Checked the old local.ini file for each of those PCs, they all had the CPUSpeed=??? entry matching the speed V 25.8 is reporting. The local.ini files were copied over from old 486/PII systems to these newer ones that replaced them.
Deleted that entry* and they are all reporting the correct speed now. Seems V 24.14 is ignoring the setting in the local.ini file, whereas V 25.8 is using it. Perhaps V 24.14 only uses that setting if it can't determine a speed, and V 25.8 uses it regardless? Thanks, Jerry *EDIT: Deleted in local.txt of course Last fiddled with by TheOutcaste on 2009-01-02 at 17:00 |
![]() |
![]() |
![]() |
#4 | |
Banned
"Luigi"
Aug 2002
Team Italia
2·74 Posts |
![]() Quote:
Luigi |
|
![]() |
![]() |
![]() |
#5 |
Jan 2009
1102 Posts |
![]() |
![]() |
![]() |
![]() |
#6 |
Oct 2008
n00bville
13258 Posts |
![]()
The estimated time of my Intel Atom has also increased by the factor 3 ... I´m trying 29 and will see if it will changes ...
|
![]() |
![]() |
![]() |
#7 | |
Oct 2008
n00bville
52·29 Posts |
![]() Quote:
Thou I think between v27 and v28 something changed in the cpu detection and that leads to wrong time estimation |
|
![]() |
![]() |
![]() |
#8 |
P90 years forever!
Aug 2002
Yeehaw, FL
1CBA16 Posts |
![]()
Bad news for you. The CPU detection code did change and the estimated completion date in 25.8 is much more accurate. Atom = not-good-for-LL.
|
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Are P-1 errors detected? | petrw1 | PrimeNet | 17 | 2018-07-04 20:13 |
Is Moore's Law wrong, or is it wrong-headed (6th time around) | jasong | jasong | 12 | 2016-05-27 11:01 |
What problems are detected | MrAskew | Information & Answers | 1 | 2010-09-24 13:48 |
Wrong CPU speed reported in mprime benchmark | James Heinrich | Software | 5 | 2009-06-13 12:56 |
laptop reporting wrong clock speed to PrimeNet | ixfd64 | Hardware | 1 | 2008-10-19 03:20 |