LinX - A simple Linpack interface

[Dua|ist]

Damn, I don't have a Vista 64 installed atm, but now I guess is the best time to install it. I'll fix this asap.

And if you uncheck the 64-bit mode, still the same result?

[burebista]

Yep, but now it tells me that is not enough memory. The bright side is that it doesn't remain memory resident.

[RJARRRPCGP]

Yep, but now it tells me that is not enough memory. The bright side is that it doesn't remain memory resident.

Dua|ist, I believe to get around the 2 GB per-process limit is to have 2 Linpack processes! Sorry.

[Dua|ist]

It loaded mine 99.9%, all 8 threads, but there is some memory bug. Refuses to run sometimes with stopped unexpectedly, error not enough memory. If I try to run with 256 mb, very small, it tells me not enough memory and kicks it up to 1748. It will only let me run at 1748, no less, and half the time when I pick 1748, it tells me not enough memory, though I have 2748 free. (I know there is 1748 limit with xp 32 bit).

But once that bug gets fixed, pretty sweet being able to load all 8 cores with one instance at max memory

At least it works on all cores. Here's the fixed version : LinX 0.5.5.1

Dua|ist, I believe to get around the 2 GB per-process limit is to have 2 Linpack processes! Sorry.

Question is, whether we need to get around that limit at all? Most systems with 4GB of RAM and more have a 64-bit OS, and x64 version of Linpack has no such limit. There are of course 32-bit OSes with 4 GB of RAM and ~3.5 GB of useable memory, but that 2 processes idea was just a temporary fix to load all cores when HT is on. Now that it can be done in a much better way via Linpack itself I don't see any reason to keep this option. The current ~1750 MB limit for 32-bit Linpack is enough to adequately stress-test any CPU, while RAM testing is not Linpack's goal anyway. If you still want to test all your memory, just run 2 instances of LinX.