Kostenlos · Netzwerk & IT-Infrastruktur

Server-Dimensionierung nach Besucherzahlen.

Schätzen Sie Spitzenlast, gleichzeitige Besucher, Anfragen pro Sekunde, Bandbreite sowie benötigte CPU und RAM aus den monatlichen Besuchern Ihrer Website.

CALCULATED IN YOUR BROWSER · NOTHING IS UPLOADED

Traffic

Visitors per month (sessions)

Pages per visit

Average visit duration (min)

Busiest day vs average day (×)

2 = the busiest day has twice the traffic of an average day. Campaigns, launches and news spikes can reach 5–20×.

Share of the day in the busiest hour (%)

4.2 % means perfectly even traffic. 8–12 % is common for regional sites; global audiences are flatter.

Busiest minute vs busiest-hour average (×)

Pages and caching

Average page weight (MB)

Everything a page downloads: HTML, scripts, styles, images, fonts.

HTTP requests per page

Static bytes and requests served by a CDN or browser cache (%)

Page views served from a full-page cache (%)

WordPress page cache, Varnish, Nginx FastCGI cache or CDN HTML caching.

Application server

CPU time per uncached page (ms)

Measure with APM or a load test. Typical: 20–80 ms for light pages, 100–400 ms for heavy CMS or shop pages.

Server response time per uncached page (ms)

Time a worker stays busy, including database and API waits.

Memory per worker or process (MB)

Base memory (OS, web server, caches) (MB)

Database memory on the same server (MB)

0 if the database runs elsewhere.

Target CPU utilisation at peak (%)

Growth headroom (%)

Recommended starting size1 vCPU · 4 GB RAMsingle server

Page views per month: 300,000
Peak page views per second: 0.82
Peak concurrent visitors: 50
Peak HTTP requests per second: 58
Uncached pages per second at origin: 0.82
Static requests per second at origin: 56.7
CPU cores needed: 0.24
Concurrent workers (PHP-FPM, Node, Puma…): 2
Memory needed: 2.2 GB
Peak bandwidth (visitors): 16.43 Mbps
Peak bandwidth (origin server): 16.43 Mbps
Monthly transfer (visitors): 750 GB
Monthly transfer (origin): 750 GB
Capacity of the recommended size: About 638,044 visitors/month (CPU-bound)

This is a planning estimate built from your assumptions, not a measurement. Confirm with a load test (k6, Locust, JMeter, Gatling) on a staging copy before buying.
Peak load, not monthly visitors, decides server size: visitors arrive unevenly, so the peak inputs matter most.
Months are averaged to 30.44 days. Data sizes are decimal (1 MB = 1,000,000 bytes).

So verwenden Sie das Tool: Server-Dimensionierung nach Besucherzahlen

Geben Sie Daten ein oder wählen Sie eine Datei. Passen Sie die Einstellungen an, erstellen Sie das Ergebnis und prüfen Sie es vor dem Kopieren oder Herunterladen.

Grenzen und unterstützte Formate

Ihre Eingaben werden auf Ihrem Gerät verarbeitet.

Technische Hinweise auf Englisch

A planning estimate from your assumptions, not a measurement; confirm with a load test. Months are 30.44 days and data sizes decimal. Database servers and multi-region designs are not sized separately. Everything is calculated in your browser; nothing is sent or probed on the network.

Monthly visitors are converted to the busiest minute using the peak-day, peak-hour and burst factors. Little’s law gives concurrent visitors and workers; CPU is uncached pages × CPU time ÷ target utilisation; bandwidth is page views × page weight.

100,000 visitors a month, 3 pages each and 2.5 MB pages peak at about 0.8 pages per second and 16 Mbps: a 1 vCPU / 4 GB server with room to spare.