There are two figures you need to bear in mind when choosing a server, concurrency and page load time. Concurrency is how many customers your server can support at any time. Individual page load time is how fast the page actual loads for a single customer.
It is possible to have:
- A slow page load time and low concurrency support (low clock speed CPU (GHz), few cores)
- A fast page load time, but low concurrency support (high clock speed CPU (GHz), few cores)
- A slow page load time, but high concurrency support (low clock speed CPU (GHz), lots of cores)
- A fast page load time and high concurrency support (high clock speed CPU (GHz), lots of cores)
You can choose your hardware based on this.
- A standard Magento demo store is capable of delivering roughly 230 uniques per GHz, per hour.
- A typical web store, with admin user activity, development activity, product addition/deletion can see this degrade by around 100%, to 115 uniques per GHz, per hour.
- A store with a poorly built/heavy template can further reduce the figure by another 100-200%, to 50 uniques per GHz, per hour.
We quote estimate figures based on a combination of 2. and 3. - but you can adjust to suit your store's build quality.
|Chassis||Total GHz||Visitors/Hour Peak||Visitors/Day Peak||Concurrent Visitors Peak||Sustained Visitors/Day|
The total GHz figure can be obtained by multiplying the CPU clock speed against the number of logical cores.
Individual Page load time
A standard Magento demo store (CE or EE – with all caches disabled) is capable of achieving average load times of:
|Chassis||CPU Speed*||Page Load Time (seconds)|
But again, a badly built/heavy template will cause this figure to increase exponentially. When we quote figures, we use the demo store template with sample data as an example.
* As Sonassi use the latest generation Intel server CPUs, the CPU speed quoted is that of the maximum sustained frequency the CPU can operate at