I put together a practical breakdown of how many users a small 1 vCPU + 2 GB RAM server can realistically handle. The answer isn’t simply “X users” because it depends heavily on the workload, application stack, caching, database usage, concurrent requests, and whether you’re serving static or dynamic content. For anyone running small self-hosted services or websites on inexpensive VPS instances, this may be useful

  • ahmedezat_katteb@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 hours ago

    The most useful number you can get is from your own stack: put your actual app on the box and hit it with k6 or wrk using a realistic mix of pages, and watch memory rather than CPU. On 2 GB the failure mode is almost always RAM: too many PHP-FPM/worker processes plus a database on default buffers, then swap thrashing and the OOM killer, long before the single core is the limit.

    What buys the most headroom on boxes this size:

    • cap the worker count (pm.max_children or the equivalent) to what actually fits in RAM
    • size the DB buffer pool deliberately instead of leaving defaults
    • zram for bursts
    • serve anything static or cacheable straight from nginx so it never touches the app

    And rate-limit or block the obvious scrapers. As someone said above, bot traffic is often the real load.