To serve a WordPress page, the host may need to run code, read data and fetch files. Each step places a different load on the server.
At HyperWP, we use HP-based servers with Intel CPUs and NVMe drives.
Page speed depends in part on how well the server can meet that load.
One server, several jobs
A server needs to run code, hold data in memory and read or write files. Those jobs are linked, but they are not the same.
The CPU works through the code. Memory keeps data close at hand. Storage holds files and data for the longer term.
If one part has to wait, the page may wait too. A fast CPU is useful, but it still needs the rest of the system to keep up.
How we build the platform
Our standard plans use Intel Silver CPUs. Our high-frequency plans use Intel Gold CPUs. NVMe drives provide the storage layer.
WP Accelerate caching helps avoid repeat work where saved results can be used. This reduces the number of requests that need PHP execution and database queries.
Hardware and workload
A server’s brand alone does not tell you how a site will feel. The available resources, the demand on them and the code on the site all matter.
A site with a few short posts has different needs from a large shop. A busy import is different from a reader opening a cached page.
The useful question is where the workload is constrained. There is no single piece of hardware that makes every site fast in every case.
Resources for page requests and site management
When you save a post or open a page, a lot happens out of view. Good hosting gives those jobs room to run. Less time spent waiting means more time for the work you came to do.
Our HP servers are the physical home for that work. Each part helps the site get on with its work.
The aim is to give the site enough CPU time, RAM and storage for its work. Caching helps reduce the load from repeat requests.