PasteZap
🌐 Nederlands
Gratis · Zonder account

Gratis · Netwerk en IT-infrastructuur

Serverdimensionering op basis van bezoekers.

Schat piekverkeer, gelijktijdige bezoekers, verzoeken per seconde, bandbreedte en de benodigde CPU en RAM op basis van het maandelijkse bezoek van uw website.

Voordat je begint

Sommige technische bedieningselementen zijn in het Engels. Unicode-tekst wordt ondersteund; formaten en uitvoertalen hangen af van de tool.

De technische limieten staan hieronder in het Engels. Controleer ze voordat je grote bestanden verwerkt of het resultaat gebruikt.

CALCULATED IN YOUR BROWSER · NOTHING IS UPLOADED

Traffic

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

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

Pages and caching

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

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

Application server

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

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

0 if the database runs elsewhere.

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
Little’s law: arrivals per hour × visit duration
Peak HTTP requests per second
58
All requests, before CDN offload
Uncached pages per second at origin
0.82
Static requests per second at origin
56.7
CPU cores needed
0.24
At 60 % utilisation with 50 % growth
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).

Zo gebruik je deze tool: Serverdimensionering op basis van bezoekers

Voer gegevens in of kies een bestand. Pas de instellingen aan, maak het resultaat en controleer het voordat je het kopieert of downloadt.

Limieten en ondersteunde formaten

Je invoer wordt op je apparaat verwerkt.

Technische opmerkingen in het Engels

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.