3 ms·
> 50,000 It's not 3.6 roentgen... Joking aside that's incredibly fascinating, I never thought that ECC memory has that much of a performance impact. Might be
by moffkalast 3y ago
> 50,000
It's not 3.6 roentgen...
Joking aside that's incredibly fascinating, I never thought that ECC memory has that much of a performance impact. Might be more optimal to just get a large jerry can of water and put that over the server as radiation shielding lol.
- toast0 3y agoECC interrupts were never a problem at reasonable counts. It's just this machine where the memory was falling apart where it was a problem. Our system was robust to a machine halting, but not so great at dealing with a machine running very very slow. Plus, it wasn't easy to connect and shut down the service (maybe we should have just killed it from IPMI, but this was the only time it happened, so learning experience). I had a similar issue one time where a Pentium III era server rebooted and came up with a comically small amount of memory, maybe 2-4 mb instead of 128 mb. That wasn't too bad, because it was a very lightly service; important to be on its own machine for reasons, but didn't need much. Just ran a little slow when it was running from swap. I think it did trigger a swap usage alert, and then it was like why is it swapping, why is it so slow, wait why doesn't it have any memory!?
- thedrexster 3y ago> It's not 3.6 roentgen... I'm told it's the equivalent of a chest x-ray... I see you, brother! :D