The HyperWP platform journal

Inside WordPress.
From server to page.

Technical notes on the hardware, database, caching and security behind our WordPress platform. This site provides a working example of how those parts interact.

HyperWP platform architecture: WordPress application, WP Accelerate caching, NVMe storage and HP with Intel compute.
HYPERWP / UNDER THE HOODPLATFORM OVERVIEW - 01
Test environmentHyperWP Business
CPU allocation3 high-frequency cores
Memory3 GB RAM
Storage25 GB Gen 5 NVMe

Notes from the platform

Under the hood.

Technical notes on WordPress performance, caching, storage and security.

Built on solid foundations

Good performance starts underneath.

Our platform combines HP servers, two Intel CPU plan families, NVMe storage and WP Accelerate caching. Each part has a different job.

Get to know the stack →
01
Compute that fits the workloadIntel Silver CPUs power our standard plans. Intel Gold CPUs power our high-frequency plans.
02
NVMe storageNVMe drives handle file and database storage. Their role depends on how much data a request needs to read or write after caching is taken into account.
03
Less repeat work with WP AccelerateCaching lets the platform reuse work where it is safe to do so. That can mean less waiting when the next visitor arrives.
04
Database caching in RAMWe give SQL caching a generous share of server memory. Keeping frequently accessed data in RAM helps reduce repeat disk reads and the time spent waiting for storage.

About this site

A working WordPress workload.

This site runs on the same platform as customer sites. Its posts, images and layouts provide a consistent workload for exploring how the server, cache and browser affect page delivery.

The test environment is listed above. Results depend on the page, cache state, server load, device and network.

What does this workload include?

The homepage, article pages, images and search give WordPress several types of work to do. The articles explain the technologies involved and the limits of what each layer can tell us.

Why use a lightweight theme?

System fonts, local images and no theme JavaScript keep the front end simple. This makes it easier to distinguish server delays from work added by the page itself.

What changes the results?

Plugins, queries, images, traffic and cache state can change the work a request creates. Device and network conditions also affect what a visitor sees. These details matter when comparing measurements.