Server calculator

Game servers

• Memory is a base for the server itself plus an amount per player, both from the game's documentation, times a factor for mods or plugins.
• CPU is the game's base core count plus one core for every so many players; a heavy mod load adds one more.
• Upload is the game's kbit/s per player times the players online. Traffic a month assumes 35% of your player cap online on average, which you can change.
• Each game's page lists its published figures, the model built from them, and the sources.

Websites and bandwidth

• Page views a month = visitors a month x pages per visit.
• Busiest page views a second = page views a month / seconds in a month x the busiest-hour factor.
• CPU time a page view = building the page (weighted by how often a cache answers it) + one request per file on the page x 1 ms; with a CDN, 5% of the file requests still reach the server.
• CPU cores = busiest page views a second x CPU time a page view / 1,000 ms, sized so the server runs at 60% at the busiest hour.
• Memory for a PHP site = PHP workers busy at the busiest moment x memory per worker + the web server + MySQL's default 128 MB buffer pool; at least 1 GB.
• Traffic a month = page views a month x page weight; with a CDN, 5% of it still leaves the server.
• Visitors online at the peak = visitors a second x session length x the busiest-hour factor.
• Planning assumptions: the busiest hour is 3 times the average hour; a server is sized to run at 60% of its CPU at that hour; with a CDN, 5% of the files still come from the server.

Page weight and requests per page are global medians from HTTP Archive; your site can be far lighter or heavier. Pages per visit comes from an ecommerce benchmark and session length from aggregated analytics; the busiest-hour factor (3), the 60% CPU target and the CPU and memory per page are planning assumptions, not measurements. Treat the result as a starting size and load-test before a launch.