LinX - a simple GUI for Intel Linpack Benchmark.

The main point of Linpack is to solve systems of linear equations of the given s
ize (Problem Size). It is designed as a benchark to test the performance of a sy
stem in GFlops - billions of floating point operation per second. But being high
ly optimized it is also the most stressful CPU testing program to date and is a
great tool in determining stability/instability of a CPU, outperforming other CP
U testing software at least time-wise. One and the same system of equations is s
olved repeatedly; if all results match each other - the CPU is stable, otherwise
the instability is obvious, since the same equations system cannot produce diff
erent solutions.
A brief overview of LinX' functionality and interface:
File -> Save Screenshot menu item. Saves main window's screenshot into program fol
der in a PNG format.
File -> Save Text Log menu item. During or after testing saves a text log with tes
ting results into program folder.
File

> Exit menu item. Exits the program. (Who'd had thought?)

Settings menu item. Opens a window with Linpack's and LinX's additional settings.
Settings window:
Main Linpack Settings:
-testing mode (32-bit/64-bit). By default is set to OS type;
-Linpack rocess priority. Setting this value higher than Normal is not recomme
nded;
-number of threads Linpack creates. By default is set to the number of logic
al processors (including HyperThreading-cores);
-data alignment. 4 KiB by default, equal to the page size in Windows OS;
-optimal Leading Dimensions. The Leading Dimensions value will be set to the
nearest odd multiple of 8 higher than or equal to the Problem Size value (suppo
sed to produce better performance)
Advanced settings. These are to be changed only if you have problems getting L
inpack to work.
-maximum Problem Size for 32-bit Linpack. Lower if on higher Problem Size/me
mory values Linpack reports not enough memory
-amound of RAM that will be left for OS when using the All memory option. Ca
n be increased to increase OS responsiveness.
LinX settings:
-auto-stop testing when an error is detected
-auto-save log file during testing (as in Linpack, lowers performance a bit)
-enable sounds upon success/fail
-tray icon and the ability to minimize LinX to tray area to save some taskba
r space
-add current date/time or date/time of testing start to screenshot and log f
iles respectively
-disable context hints
External Applications Import:
-monitoring data source (None, Everest, Speedfan):
Allows LinX to receive some data like core temperatures, CPU voltage, frequency,
CPU fan RPM and +12 V voltage from either Everest or Speedfan. The temperature
of the hottest core as well as CPU voltage and frequency (when importing data fr
om Everest) are displayed in status bar during testing, other values are used to

create graphs. To import data from Everest go in Everest to File -> Preferences.
.. -> External Applicatons and check the Enable shared memory checkbox. For Speedfa
n you need to first fill in the values in the "Speedfan.ini" file in LinX direct
ory. These values are numbers of temperatures/voltages/fan speeds as they are di
splayed in Speedfan, from top to bottom starting with 1. For example, if core0 t
emperature in Speedfan is listed 5th from top set in the INI file CPU_core0_num=
5 and so on.
Note that Everest or Speedfan should be running with LinX for all this to work.
-stop the testing once the desired temperature is reached. If LinX is gettin
g data from Everest or Speedfan testing will stop when the temperature reaches t
his threshold to prevent CPU from overheating.
Graphs -> Create menu item. Allows you to choose which graphs to create during tes
ting: you can choose from CPU temperature, CPU fan speed, CPU vcore and +12V vol
tage values. To display the graphs use the Graphs -> Display menu item. Graph wind
ows can be resized in real-time, graphs can be saved by double-clicking on them
in the corresponding window.
? menu item. Opens a window with some info about the program and a very short ve
rsion of this file.
Problem Size & Memory to use fields. The first one is the amount of equations to sol
ve, the second - the corresponding amount of memory that will be allocated by Li
npack for this Problem size. You can either set the Problem size and the amount
of memory to be used will be calculated automatically or vice versa. There is al
so an All [memory] button available to use all free physical memory. The effective
ness of finding errors as well as the amount of stress to the processor increase
with increased memory usage/Problem size.
1 MiB = 1024 KiB = 1024^2 bytes
Times to run. This is how many times the test will be run. Once again, the more th
e better. To consider a CPU fully stable you should set this to at least 50-100,
for quick testing lower values are acceptable.
Start & Stop buttons. Used to start and stop the testing process respectively.
Status field/progressbar. Displays the amount of available memory before testing
, the elapsed/remaining/finish time during testing (these can be switched by cli
cking on the field or even turned completely off by double-clicking if you need
another 100th of GFlops) and the result (success or fail) with the time spent on
testing after testing.
Bottom status bar. Displays some useful information like the current test # and
the total number of tests, maximum performance in GFlops so far, testing mode (3
2-bit or 64-bit), current number of threads, and with Everest or Speedfan data CPU temp, voltage and frequency. There's also table(default LinX view)/log(Linp
ack) toggle button available after the testing has finished.
Double-clicking the main window will make it stay on top.
List of available command-line keys: LinX.exe /?
If you made it this far you're very patient. I hope you enjoyed reading this Rea
dMe as much as I did writing it. Thanks for reading!