Tweet
While setting SPEED to % makes sense on one single server and I understand the GHz for trying to match across servers, there is still a problem that the GHz can be somewhat different depending on the CPU (age) on different servers accumulated over time.
Since CloudLinux can control the CPU usage, would it not be possible for you to have a benchmark CPU script built in that tries to use the CPU like crazy to complete a certain task, limit that script to one single core (100%) in execution and then measure how long it took and then compute a CPU benchmark value that webhosts can use to even better match the CPU performance of their hosting plans to different hardware so that clients get the same speed no matter which server they are on?
This way there would be an "x"-factor that would take the guesswork out of matching plans to different servers.
Since CloudLinux can control the CPU usage, would it not be possible for you to have a benchmark CPU script built in that tries to use the CPU like crazy to complete a certain task, limit that script to one single core (100%) in execution and then measure how long it took and then compute a CPU benchmark value that webhosts can use to even better match the CPU performance of their hosting plans to different hardware so that clients get the same speed no matter which server they are on?
This way there would be an "x"-factor that would take the guesswork out of matching plans to different servers.
Comment