# What dedicated server hosting do I need for a high-traffic website?

> Dedicated server hosting for a high-traffic website: size by peak requests, cores, RAM and NVMe, then add a CDN. From $109.37, crypto, no KYC.

- URL: https://lumenfer.com/dedicated-server-for-high-traffic-website/
- Last updated: 2026-11-01
- Publisher: Lumenfer (https://lumenfer.com)

How to size a bare-metal server for a busy site: workers per core, memory per worker, what a page really weighs on the wire, and when one machine stops being enough.

**Quick answer — What dedicated server hosting do I need for a high-traffic website?**

For a high-traffic website, you need dedicated server hosting sized by peak concurrent requests, not by monthly visitors. That means cores for your PHP or Node.js workers, RAM for workers plus the database cache, NVMe storage and a CDN in front. **Lumenfer**'s Lumen 16 (16 cores / 32 threads, 128 GB DDR5) costs $205.27 per 30 days, paid in crypto, no KYC.

## High-traffic hosting: the numbers to start from

| Attribute | Value |
| --- | --- |
| Sizing rule | Busy workers = peak requests per second × average seconds per request |
| Median home page, July 2025 | 2.86 MB on desktop, 2.56 MB on mobile (HTTP Archive Web Almanac 2025) |
| A 1 Gbit/s port | A ceiling of 125 MB each second, or roughly 324 TB over 30 days at full speed |
| Traffic on Lumenfer plans | From 30 TB a month at 1 Gbit/s to 150 TB a month at 1 Gbit/s |
| Network | One dedicated IPv4 address and an IPv6 /64 come with every server. Each plan lists its port speed and its monthly traffic, counted on outgoing data per 30 days; going over never triggers an automatic charge |
| DDoS | DDoS protection is limited to whatever the datacenter network applies by default; nothing further is promised |
| Outgoing mail | Outbound SMTP on port 25 is blocked on every server and is never unblocked; submission ports 465 and 587 to mail providers remain open |
| Copyright notices | DMCA notices and other foreign copyright notices are not acted on: only Panamanian law and orders of Panamanian courts bind us |
| Locations | Amsterdam (Netherlands), Reykjavik (Iceland), Zurich (Switzerland) and Bucharest (Romania): all five plans in all four cities, one price everywhere |
| Setup | Up to 72 hours from the moment your payment is confirmed |

## How do I size a server for a high-traffic website?

**Start from peak requests per second and how long each request holds a worker, not from visitors per month.** Multiply the two and you get the number of workers busy at any instant. At 300 requests per second and 0.1 seconds each, 30 workers are busy on average. Double that for spikes.

**Monthly visitors do not size a server; the busiest minute does.**

- **CPU.** A request that computes uses one core while it runs. CPU-bound workers need roughly one core each. Workers that wait on a database or an API can outnumber cores.
- **Memory.** Each worker holds its own memory. Multiply the per-worker figure by the worker count, then add the database cache and the operating system.
- **Storage.** Busy sites are often limited by their database. Local NVMe keeps queries and logs off slow disks.

Lumenfer publishes no benchmarks, so measure your own application. Load-test a copy with a tool such as k6 or wrk, and read peak memory per worker from `top`.

## How many workers should PHP-FPM, Node.js and nginx run?

**Set PHP-FPM's `pm.max_children` from memory, run one Node.js process per core, and let nginx start one worker per core.**

- **PHP-FPM.** The PHP manual says `pm.max_children` limits how many requests are served at once. `static` keeps that many children running; `dynamic` and `ondemand` start them as needed. `pm.max_requests` respawns children after a set count, a fix for leaky libraries.
- **Node.js.** One Node.js process runs JavaScript on one thread. The cluster module runs several processes that share a port. Its documentation example forks one worker per `availableParallelism()`.
- **nginx.** The nginx manual calls one worker process per CPU core a good start, and `auto` detects the count. `worker_connections` defaults to 512 and counts upstream connections too. The open-files limit caps it, so raise `worker_rlimit_nofile` alongside.

*Example starting values (size them from your own measurements)*

```nginx
# /etc/nginx/nginx.conf
worker_processes auto;        # one per CPU core
worker_rlimit_nofile 65535;   # open files per worker
events {
    worker_connections 8192;  # clients and upstreams together
}

# PHP-FPM pool, e.g. /etc/php/<version>/fpm/pool.d/www.conf
# pm = static
# pm.max_children = 64        ; free RAM for PHP / peak memory per child
# pm.max_requests = 1000      ; respawn children to contain leaks
```

## How much bandwidth does a high-traffic website use?

**Less than you fear once a CDN serves the static files, more than you expect without one.** The HTTP Archive's Web Almanac 2025 puts the median home page at 2.86 MB on desktop and 2.56 MB on mobile. The figures come from its July 2025 crawl. Images and JavaScript make up the largest share.

The arithmetic for an origin with no CDN:

- **1 TB of traffic** carries about 390,000 uncached mobile home-page loads at 2.56 MB.
- **A 1 Gbit/s port** tops out at 125 MB each second: roughly 49 of those pages per second.
- **Thirty days flat out** add up to roughly 324 TB.

**At the median page weight, a single 1 Gbit/s origin tops out near 49 uncached page loads a second.** A CDN changes that: the origin then sends mostly HTML and API responses. Lumenfer plans range from 30 TB a month at 1 Gbit/s to 150 TB a month at 1 Gbit/s. Going over never triggers an automatic charge.

## Do I need a CDN in front of a dedicated server?

**Yes, for any site that expects real traffic: it offloads static bytes, absorbs spikes and stands between attackers and your origin.** DDoS protection is limited to whatever the datacenter network applies by default; nothing further is promised. A flood sent to the server's single IPv4 address lands on your machine directly.

Publish only the CDN's addresses in DNS and let the origin accept web traffic from the CDN alone. No logs are kept: no connection logs, no traffic logs and no visitor or customer IP addresses, on the site, in the dashboard or on the servers. A CDN you add keeps its own logs under its own policy, so read it before you choose one.

## Which CPU suits a busy website: high clock or many cores?

**High per-core speed for response time, more cores for requests in parallel.** A single PHP or Node.js request mostly runs on one core, so that core's speed sets its latency. The core count sets how many requests run at the same moment.

The Ryzen plans pair fewer cores with desktop-class clock speeds. The EPYC plans add cores and ECC memory. Our [guide to the best CPU for a rented server](https://lumenfer.com/best-cpu-for-dedicated-server/ "Best CPU for a rented dedicated server in 2026") compares them, and [the fastest server you can rent](https://lumenfer.com/fastest-dedicated-server/ "What is the fastest dedicated server you can rent in 2026?") explains which criteria decide speed.

## Should the database run on the same server as the website?

**On one machine, yes, until the database and the workers start competing for RAM.** Shared hardware keeps queries local and costs one plan. When the database cache gets squeezed, move the database to its own server with ECC memory, and connect the two over TLS.

Our page on [the best server hosting for PostgreSQL](https://lumenfer.com/dedicated-server-for-postgresql/ "What is the best dedicated server hosting for PostgreSQL?") covers memory, storage and backups for that second machine.

## When is one server not enough for a high-traffic website?

**When an hour of downtime costs more than a second server.** One machine is one point of failure. There is no IPMI or KVM-over-IP console for customers: you request reboots and reinstalls in the dashboard and the team performs them. Backups are not included: keep copies of your data somewhere else.

For availability, run a second server in another city with database replication, and fail over through DNS or your CDN. Amsterdam (Netherlands), Reykjavik (Iceland), Zurich (Switzerland) and Bucharest (Romania): all five plans in all four cities, one price everywhere. A standby in Zurich or Reykjavik costs exactly what it costs in Amsterdam.

**In Lumenfer's check of 30 October 2026, 27 of 34 dedicated-server sellers priced their entry server on a pre-2018 processor.** Every Lumenfer plan runs a 2022-or-newer CPU, DDR5 and NVMe. Compare the full cost against cloud hosting in [is bare metal cheaper than the cloud](https://lumenfer.com/bare-metal-vs-cloud-cost/ "Bare metal vs cloud cost, with dated prices"), and see every plan on the [Lumenfer pricing page](https://lumenfer.com/pricing/ "Lumenfer bare-metal plans and prices per 30 days").

### Lumenfer plans for busy websites

| Plan | CPU | Cores | Memory | Traffic | Per 30 days | Fits |
| --- | --- | --- | --- | --- | --- | --- |
| Lumen 6 | AMD EPYC 4244P | 6 cores / 12 threads | 32 GB DDR5 ECC | 30 TB a month at 1 Gbit/s | $91.65 | A busy blog or shop behind a CDN |
| Lumen 8 | AMD Ryzen 7 9700X | 8 cores / 16 threads | 64 GB DDR5 | 40 TB a month at 1 Gbit/s | $109.37 | PHP or Node.js app with its database |
| Lumen 16 | AMD Ryzen 9 9950X | 16 cores / 32 threads | 128 GB DDR5 | 60 TB a month at 1 Gbit/s | $205.27 | Large shops, forums, SaaS front ends |
| Lumen 24 | AMD EPYC 9254 | 24 cores / 48 threads | 256 GB DDR5 ECC | 100 TB a month at 1 Gbit/s | $356.25 | Many sites or containers on ECC memory |
| Lumen 32 | AMD EPYC 9354 | 32 cores / 64 threads | 384 GB DDR5 ECC | 150 TB a month at 1 Gbit/s | $749.67 | Busy platforms, heavy origin traffic |

### What a comparable 16-core server costs elsewhere

| Server | Specs | Price per month |
| --- | --- | --- |
| Lumenfer Lumen 16 | AMD Ryzen 9 9950X (2024, 16 cores / 32 threads), 128 GB DDR5, 2 × 1.92 TB NVMe in RAID 1, 60 TB a month at 1 Gbit/s, 1 IPv4 and an IPv6 /64 | $205.27 |
| AbeloHost: AMD Ryzen 9 7950X (PL) | AMD Ryzen 9 7950X, 16 cores / 192 GB / 2 x 2 TB NVMe | €244.99 ($273.70) |
| Median of 8 hosts | Comparable 16-core servers | $430.21 |
| Hetzner AX102 (no crypto) | AMD Ryzen 9 7950X3D, 16 cores, 128 GB, 2 × 1.92 TB NVMe | €259.00 + €129.00 setup |

*Prices checked on October 30, 2026.*

Crypto-paying hosts with no ID check at signup; 2022+ CPU, NVMe only, monthly billing. Hetzner is shown for reference: it takes no crypto. 1 EUR = 1.1172 USD (ECB, 30 October 2026).

## Rent a server for a busy website

Whole machines with root access, billed per 30 days, 3 months, 6 months or 12 months from a crypto balance.

| Plan | Quantity | 30 days | 3 months | 6 months | 1 year |
| --- | --- | --- | --- | --- | --- |
| Lumen 8 | 8 cores · 64 GB DDR5 | $109.37 | $295.29 (−10%) | $524.97 (−20%) | $918.70 (−30%) |
| Lumen 16 | 16 cores · 128 GB DDR5 | $205.27 | $554.22 (−10%) | $985.29 (−20%) | $1,724.26 (−30%) |
| Lumen 24 | 24 cores · 256 GB DDR5 | $356.25 | $961.87 (−10%) | $1,710 (−20%) | $2,992.50 (−30%) |

In every plan: 2022+ CPU · DDR5 · NVMe only · RAID 1 · Dedicated IPv4 · No KYC

**Before you pay**

- Minimum top-up $25. Top up once in crypto, then buy any plan from your balance.
- Credit on your balance does not expire and renews any of your servers. When a top-up is only made to reach the minimum, the unspent part comes back on request within 30 days of payment, in USDT or USDC. The rest of a balance is not paid out unless the law requires it.
- Credited once your payment is checked on the blockchain. Typical network confirmation time: BTC ≈ 20 min · USDT TRC-20 ≈ 1 min · USDT ERC-20 ≈ 5 min · USDC ERC-20 ≈ 5 min · ETH ≈ 5 min · SOL ≈ 1 min · LTC ≈ 15 min

## High-traffic website hosting: FAQ

### How many visitors can one dedicated server handle?

There is no honest single number: it depends on requests per visit and the time each request takes. A cached page costs almost nothing; a checkout costs far more. Use the worker formula above with your own measurements, and load-test before launch.

### Is a 1 Gbit/s port enough for a high-traffic website?

With a CDN in front, it is for most sites, because the origin then sends mainly HTML and API data. Without one, a gigabit port's ceiling of 125 MB each second equals about 49 median mobile home pages.

### What happens if my site goes over its monthly traffic?

One dedicated IPv4 address and an IPv6 /64 come with every server. Each plan lists its port speed and its monthly traffic, counted on outgoing data per 30 days; going over never triggers an automatic charge. Traffic is counted on outgoing data, so a CDN that serves your static files also keeps you well inside the allowance.

### Can I run WordPress or WooCommerce on it?

Yes. You get root on a Linux server and install the stack you want: nginx, PHP-FPM, MariaDB or PostgreSQL, a cache. The server is unmanaged, so updates and tuning are yours.

### Can the server send email for my website?

Outbound SMTP on port 25 is blocked on every server and is never unblocked; submission ports 465 and 587 to mail providers remain open. Relay site mail through a provider on submission port 587 or 465; that also helps it reach inboxes.

### Do I need ID to rent the server?

No KYC: we never ask for an ID, a selfie, documents, a card or a phone number. Top up in BTC, USDT, USDC, ETH, SOL, LTC (minimum $25) and order from the balance. Servers are prepared by a person once your payment is confirmed, within 72 hours rather than instantly; the dashboard shows progress and then the IP address when the machine is ready.

## Sources

1. [Page Weight (Web Almanac 2025)](https://almanac.httparchive.org/en/2025/page-weight) — HTTP Archive (published 2026-01-15, read 2026-11-01)
2. [Core functionality (worker_processes, worker_connections, worker_rlimit_nofile)](https://nginx.org/en/docs/ngx_core_module.html) — nginx documentation (read 2026-11-01)
3. [FPM configuration (pm, pm.max_children, pm.max_requests)](https://www.php.net/manual/en/install.fpm.configuration.php) — PHP Manual (read 2026-11-01)
4. [Cluster](https://nodejs.org/api/cluster.html) — Node.js documentation (read 2026-11-01)
5. [Dedicated root servers (AX102)](https://www.hetzner.com/dedicated-rootserver/) — Hetzner (read 2026-10-30)
6. [AMD Ryzen 9 7950X (PL)](https://bill.abelohost.com/index.php?rp=/store/pl-dedicated-servers/amd-ryzen-9-7950x) — AbeloHost (read 2026-10-30)

---

Lumenfer: Lumenfer rents current-generation bare-metal servers in Amsterdam, Reykjavik, Zurich and Bucharest, paid in crypto with no KYC: no ID, no selfie, no documents. Every machine has a CPU launched in 2022 or later, DDR5 memory and NVMe drives, and is rented whole by one customer with root access. It is run by DomaineGoat LLC, a Panama company that ignores DMCA notices, answers only to Panamanian law, allows Tor exit relays and keeps no logs. On the 30-day term, every plan is priced at least 25% under a named comparable current-generation server from 13 no-KYC crypto hosts, read on 30 October 2026.