4 ms·
in my (limited) experience this only happened with GIGABYTE servers very weird behavior, I'd prefer my servers to crash instead of lowering frequency to 400MHz
by tryauuum 2y ago
in my (limited) experience this only happened with GIGABYTE servers
very weird behavior, I'd prefer my servers to crash instead of lowering frequency to 400MHz.
- dijit 2y agoI've seen it on nearly every brand, I have some Lenovo Servers in the basement that also down-clock if both PSU's aren't installed. I have alerts on PSU's and frequency for this reason. The servers are so cheap that overcommitting them by double is still significantly cheaper than using cloud hosting, which tends to have the same issue only monitoring it is harder. Though most people using cloud seem to be happy not to know and it's been a known thing that there's a 5x variation between instances of the same size on AWS.: https://www.brendangregg.com/Slides/AWSreInvent2017_performance_tuning_EC2.pdf https://www.brendangregg.com/Slides/AWSreInvent2017_performa...
- jeffbee 2y ago> I'd prefer my servers to crash instead of lowering frequency to 400MHz. 100% agreed. There is nothing worse than a slow server in your fleet. This behavior reeks of "pet" thinking.
- formerly_proven 2y agoStuff like this just comes up from time to time as soon as you run a four digit and up number of systems.