It is just like in some previous versions, Linpack's text log can be saved during testing, so one can see how far it went in case everything hangs or throws a blue screen. I think it was davidk21770 who missed this feature.
No, the impact only affects GFlops numbers slightly. Shouldn't be noticeable at all (including error detection and heating effectiveness), but I've probably become too paranoid about those numbers during LinX' development while trying to minimize its impact on Linpack's performance.
This is probably the most important Linpack's setting. It determines the dimensions of a matrix (or a linear equations system, whichever you like best) that is to be solved. The higher the Problem Size number the more CPU stress, more memory consumption, longer time to solve each test.Originally Posted by omiez
I really can not suggest you an universal value for it. Basically it is the higher the better, but in some cases you might want to run LinX with lower values of it, for example during initial OC attempts to avoid BSODs, etc. The default value of 10000 is, let's say, a recommended minimum. Maybe you should play with it a little and determine your own testing methodology.![]()
Bookmarks