<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bhavin Patel</title>
    <description>The latest articles on DEV Community by Bhavin Patel (@bhavin_patel_49c69c9e8589).</description>
    <link>https://dev.to/bhavin_patel_49c69c9e8589</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4247045%2F743fb8d9-e694-4f58-9e07-605236a426dc.jpg</url>
      <title>DEV Community: Bhavin Patel</title>
      <link>https://dev.to/bhavin_patel_49c69c9e8589</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bhavin_patel_49c69c9e8589"/>
    <language>en</language>
    <item>
      <title>How I handle ~1M requests a day on 1 vCPU and 2GB RAM (and keep bots out without user accounts)</title>
      <dc:creator>Bhavin Patel</dc:creator>
      <pubDate>Mon, 16 Nov 2026 07:09:55 +0000</pubDate>
      <link>https://dev.to/bhavin_patel_49c69c9e8589/how-i-handle-1m-requests-a-day-on-1-vcpu-and-2gb-ram-and-keep-bots-out-without-user-accounts-5bhg</link>
      <guid>https://dev.to/bhavin_patel_49c69c9e8589/how-i-handle-1m-requests-a-day-on-1-vcpu-and-2gb-ram-and-keep-bots-out-without-user-accounts-5bhg</guid>
      <description>&lt;p&gt;I run a &lt;a href="https://tempgbox.net/" rel="noopener noreferrer"&gt;Tempgbox&lt;/a&gt; : free temporary email service on one vCPU and 2GB of RAM. Django, PostgreSQL, Redis, Celery. It serves around a 1 million+ requests a day. Still i notice that backend use only 500 Mb ram and 1.5 GB ram free.&lt;/p&gt;

&lt;p&gt;Four changes made the biggest difference for such a small server.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cloudflare in front.&lt;/strong&gt; I put Cloudflare in front of everything as a proxy. Most requests are for frontend pages, and Cloudflare caches those, so they never reach my server. That alone took a lot of load off it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DRF to Django Ninja.&lt;/strong&gt; I migrated the API from Django REST Framework to Django Ninja, which has built-in async support. I’m still learning how much that gives me, but it was the right direction for an API that does a lot of waiting.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cleaning up guest users.&lt;/strong&gt; Most of my users are guests, so guest accounts pile up fast. Now I delete a guest user as soon as their token expires. The database stays small, and I stopped paying to store people who were gone anyway.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Redis, with regular cleanup.&lt;/strong&gt; I use Redis for short-lived data, and I clean it up on a schedule instead of letting it grow. With only 2GB of RAM, Redis can quietly eat memory that the rest of the stack needs, so I treat it like a cache that must stay small, not a place to dump things.&lt;/p&gt;

&lt;p&gt;I’m curious what other people with tiny servers did first. Caching, cleanup, or something else?&lt;/p&gt;

</description>
      <category>django</category>
      <category>python</category>
      <category>web</category>
      <category>performance</category>
    </item>
  </channel>
</rss>
