
Reducing the size and quantity of data transferred to and from the server will remove this bottleneck. Some sites, depending on the hosting provider, may also hit caps regarding cumulative data transfer.
Network: During periods of high traffic, the network throughput required to fulfill user requests can exceed capacity. Offloading serving to other infrastructure, reducing expensive operations, and limiting the quantity of requests will reduce CPU utilization. The CPU utilization of serving a single request is negligible, but doing this at the scale encountered during traffic spikes can sometimes overwhelm a server. Server performance often degrades once CPU usage reaches ~80-90%, and becomes more pronounced as usuage gets closer to 100%. CPU: CPU usage that is consistently over 80% should be investigated and fixed. Identifying which of these is the bottleneck makes it possible to focus efforts on the most impactful mitigations.
When traffic overloads a server, one or more of the following can become a bottleneck: CPU, network, memory, or disk I/O. If you have questions or feedback on this guide, or you want to share your own tips and tricks, please leave a comment in PR #2479.