Uhm, actually not. At least it isn't for Core i7 with HT on and Linpack being run in all 8 threads. Running Linpack on a Core i7 in only 4 threads, however, would indeed result in lower GFlops (this is normal).
LinX is supposed to detect the change in # of logical processors (when turning HT on/off) and set the number of Linpack threads to the actual value.
As for the i9 of yours, it looks really weird. Maybe it'll be possible to do some Linpack tweaking to see if anything changes. Once I implement this, you'll be the first to know. ;)
Sure, if you have HT on, 16 threads is way to go. As already mentioned, LinX should default to 16 threads on an i7 PC on the first run.Quote:
Originally Posted by Bitgod
What you said about the settings not being saved is interesting indeed. Never heard of such an issue and never experienced it myself. I can't imagine what could be preventing it from saving a dozen of string into an ini-file… Thanks for the observation, I've gotta check it.Quote:
Originally Posted by Bitgod
UAC is turned off by me, but never heard of LinX having issues with it. Any chance you can turn it on and see if the bug you mentioned will re-appear?