		<div class="wpcnt">
			<div class="wpa">
				<span class="wpa-about">Advertisements</span>
				<div class="u top_amp">
							<amp-ad width="300" height="265"
		 type="pubmine"
		 data-siteid="173035871"
		 data-section="1">
		</amp-ad>
				</div>
			</div>
		</div><p dir="ltr">For most backend services, Python is the faster way to ship and Rust is the faster way to run. Rust makes sense when a service is bound by CPU, memory, or tail latency, such as a proxy, a cache, or a sync engine. Python makes sense when the bottleneck is the database, the network, or developer time. The two are also increasingly combined, with Rust doing the heavy lifting inside Python libraries. This guide compares them on speed, concurrency, safety, cost, and team factors, using real company examples and avoiding invented benchmark numbers.</p>
<h2 dir="ltr">First, a Warning About Benchmarks</h2>
<p dir="ltr">Many Python-versus-Rust articles quote framework benchmark tables. Be careful with them. The TechEmpower Framework Benchmarks repository on GitHub was archived on March 24, 2026 and is read-only. The last official round, Round 23, was announced on March 17, 2025, on new Microsoft-provided servers with 56 cores and 64GB of memory. TechEmpower said the top frameworks improved about threefold in practical network-bound tests. The benchmark is synthetic, the implementations were contributed by vendors and communities, and database-bound tests narrow the gaps between languages. This research could not retrieve per-framework figures for Axum, Actix, FastAPI, or Django, so none are quoted here. Treat any specific requests-per-second number you see as a snapshot, not a ranking.</p>
<h2 dir="ltr">What Changed in Python</h2>
<h3 dir="ltr"><strong>Free-Threaded Python Is Officially Supported</strong></h3>
<p dir="ltr">The biggest shift is concurrency. PEP 779 is marked Final (resolved June 16, 2025) and defines three phases: experimental free-threaded builds in Python 3.13, officially supported but optional in Python 3.14, and a future phase where free-threading becomes the default. That last phase needs another proposal and has not happened.</p>
<p dir="ltr">Python 3.14 was released on October 7, 2025. Its documentation says the single-thread penalty for free-threaded builds is roughly 5 to 10 percent. The free-threading how-to notes that overhead varies from about 1 percent on macOS aarch64 to 8 percent on x86-64 Linux. It also warns that importing a C extension not marked compatible re-enables the Global Interpreter Lock (GIL). To check, run a one-line script that prints the result of the sys._is_gil_enabled function, or use the PYTHON_GIL=0 setting to force the GIL off.</p>
<h3 dir="ltr"><strong>Other 3.14 Features</strong></h3>
<p dir="ltr">Python 3.14 added a concurrent.interpreters module for subinterpreters (PEP 734) with an InterpreterPoolExecutor, though the documentation notes limits such as unoptimized startup and higher memory use. macOS and Windows binaries support the experimental JIT. An opt-in tail-call interpreter built with Clang 19 or later showed a geometric mean of 3 to 5 percent faster on the pyperformance suite, which the documentation calls preliminary.</p>
<h3 dir="ltr"><strong>Python 3.15</strong></h3>
<p dir="ltr">The Register reported on May 11, 2026 that Python 3.15 beta 1 shipped with a JIT that gave a mean speedup of 8 to 9 percent on x86-64 Linux and 12 to 13 percent on Apple silicon, with some code up to 15 percent slower. The final release was slated for October 1, 2026, and this article could not confirm as of October 17, 2026 that it has shipped.</p>
<h2 dir="ltr">Where Rust Wins</h2>
<h3 dir="ltr"><strong>Predictable Latency and Memory</strong></h3>
<p dir="ltr">Rust has no garbage collector. Discord&#8217;s 2020 engineering post about its Read States service, which moved from Go to Rust, is the best-known illustration. Go&#8217;s garbage collector forced a run at least every two minutes, causing latency and CPU spikes. After the port, completed in May 2019, Rust beat Go on latency, CPU, and memory with no spikes, and the team raised the cache to 8 million read states. The caveat is that this was a cache-heavy single service, and the comparison was Go versus Rust, not Python versus Rust.</p>
<h3 dir="ltr"><strong>Infrastructure-Level Throughput</strong></h3>
<p dir="ltr">Cloudflare built Pingora in Rust to replace NGINX in its edge network. Its September 2022 post says the proxy handles over a trillion requests per day, uses about 70 percent less CPU and 67 percent less memory at the same traffic, and cut median time to first byte by about 5 milliseconds and the 95th percentile by about 80 milliseconds. Connection reuse for one customer rose from 87.1 to 99.92 percent. These are company-reported results for a very specific workload.</p>
<h3 dir="ltr"><strong>Correctness</strong></h3>
<p dir="ltr">Dropbox rewrote its desktop sync engine from Python, called Sync Engine Classic, to Rust, called Nucleus, over about four years. Its March 2020 post cites correctness and testability, not raw speed, as the reasons, and says &#8220;Rust has been a force multiplier.&#8221; The post gives no speedup figure.</p>
<h2 dir="ltr">Where Python Still Wins</h2>
<h3 dir="ltr"><strong>Time to Market and Ecosystem</strong></h3>
<p dir="ltr">The Stack Overflow 2025 Developer Survey found Python used by 57.9 percent of all respondents, up seven points from 2024, while Rust was used by 14.8 percent. Rust was the &#8220;most admired&#8221; language at 72 percent. Admiration is not adoption, and the survey data say nothing about backend performance.</p>
<h3 dir="ltr"><strong>Pragmatic Tuning</strong></h3>
<p dir="ltr">Instagram&#8217;s engineering team stayed on Python and Django and tuned instead of rewriting. Its post (undated on the page, from about 2017 per its listing) says that disabling Python&#8217;s garbage collector gave about a 10 percent capacity gain, that per-worker shared memory grew from 140MB to 225MB, and that about 25 percent of RAM was saved across the fleet. It is old, but it shows that a mature Python service can often gain more from profiling than from a rewrite.</p>
<h3 dir="ltr"><strong>When the Database Is the Bottleneck</strong></h3>
<p dir="ltr">If a request spends most of its time waiting on a database or an external API, a faster language changes little. The TechEmpower caveat above makes the same point.</p>
<h2 dir="ltr">The Hybrid Path: Rust Inside Python</h2>
<p dir="ltr">The most practical answer is often both. Pydantic V2&#8217;s validation core is written in Rust (the pydantic-core package), and its authors claimed in April 2023 that it was &#8220;5-50x faster than Pydantic V1,&#8221; though the page gives no methodology. PyO3, a library for writing Python extensions in Rust, lists polars, pydantic-core, orjson, tokenizers, cryptography, and granian among example projects. Its guide, for version 0.29.3, requires Rust 1.83 or later, and the maturin tool builds and publishes the packages. The exact maturin commands were not verified from documentation for this article, so follow the PyO3 guide.</p>
<p dir="ltr">This approach lets a team keep Python for the application and move only the hot loop into Rust, often one function at a time.</p>
<h2 dir="ltr">Decision Framework</h2>
<h3 dir="ltr"><strong>Choose Python When</strong></h3>
<p dir="ltr">The service is mostly I/O-bound, the team already knows Python, the product is still changing quickly, or you depend on its data and machine learning libraries.</p>
<h3 dir="ltr"><strong>Choose Rust When</strong></h3>
<p dir="ltr">You are building a proxy, gateway, cache, or sync engine, tail latency matters, memory per connection is costly, or the cost of a bug in production is high.</p>
<h3 dir="ltr"><strong>Choose the Hybrid When</strong></h3>
<p dir="ltr">You have a working Python service and a profiler showing one or two hot paths.</p>
<h2 dir="ltr">The Cost of Learning Rust</h2>
<p dir="ltr">The State of Rust 2025 survey, with 7,156 completed responses, reported that debugging concern fell from second to fourth place, and that compile times remain a productivity issue. It gave no numeric data on learning curve in the text reviewed. Hiring and onboarding costs are a real factor, and this research did not find hard figures on them.</p>
<h2 dir="ltr">A Practical Migration Plan</h2>
<ol dir="ltr">
<li>Profile the Python service and find where time actually goes.</li>
<li>Try cheaper fixes first, such as caching, query tuning, and async I/O.</li>
<li>Test free-threaded Python 3.14 for CPU-bound threads, checking that your C extensions are compatible.</li>
<li>If one function dominates, rewrite it in Rust with PyO3.</li>
<li>Move whole services to Rust only when the evidence supports it.</li>
</ol>
<h2 dir="ltr">How to Run a Fair Comparison on Your Own Workload</h2>
<p dir="ltr">Because published benchmark tables are snapshots, the most reliable test is your own. Pick one realistic endpoint, such as a request that reads from your database, transforms the result, and returns JSON. Build it in both languages with the frameworks you would actually use. Run the same load against both on the same hardware, and record median latency, 99th percentile latency, memory use, and CPU use under steady load, not just peak requests per second. Include a database call, since TechEmpower&#8217;s own results show that database-bound tests narrow the gaps between languages. Repeat the test with realistic data sizes. If the difference is small compared with your team&#8217;s cost to maintain two codebases, the answer is clear.</p>
<h2 dir="ltr">Questions About Team and Cost</h2>
<p dir="ltr">Speed is only one input. Ask how many engineers on your team can read and review Rust code today, and how long a new hire takes to become productive in it. The State of Rust 2025 survey notes that compile times remain a productivity issue, which affects feedback loops. On the Python side, ask whether the work involves libraries for data or machine learning that have no Rust equivalent of the same maturity. The Stack Overflow figures, 57.9 percent for Python against 14.8 percent for Rust among all respondents, say nothing about quality but do suggest the size of each hiring pool.</p>
<h2 dir="ltr">A Rule of Thumb</h2>
<p dir="ltr">Use Python until a measurement says otherwise. When the profiler points at a small hot path, move that path to Rust through PyO3 before considering a full rewrite. When a new service is a proxy, a cache, or anything where tail latency and memory per connection are the product, start in Rust. That mirrors the company examples above: Cloudflare and Discord built latency-sensitive components in Rust, while Instagram kept Python and tuned it.</p>
<h2 dir="ltr">What Free-Threading Means for Your Choice</h2>
<p dir="ltr">Free-threaded Python changes one old argument, that the GIL stops Python using several cores in a single process. With a free-threaded build, threads can run in parallel, at the price of the 5 to 10 percent single-thread penalty the documentation cites and the need for compatible extensions. That makes a Python service more competitive for CPU-bound work than it was, but it does not erase Rust&#8217;s advantages in memory use and latency predictability. Test your actual dependencies first, since one incompatible extension can re-enable the GIL.</p>
<h2 dir="ltr">Common Mistakes in This Debate</h2>
<p dir="ltr">Do not compare a tuned Rust service with an untuned Python one, or the reverse. Do not quote a benchmark without knowing whether the test hit a database. Do not assume a rewrite will pay for itself, since Dropbox&#8217;s four-year effort was justified by correctness, not speed. And do not treat the languages as exclusive, since pydantic-core, orjson, and polars are Rust inside Python projects that millions of developers use without writing Rust.</p>
<h2 dir="ltr">Frequently Asked Questions</h2>
<h3 dir="ltr">Is Rust faster than Python for backends?</h3>
<p dir="ltr">Usually, for CPU-bound work. For database-bound services the gap often shrinks.</p>
<h3 dir="ltr">Is the GIL still a problem in Python?</h3>
<p dir="ltr">Python 3.14 officially supports free-threaded builds with a single-thread penalty of roughly 5 to 10 percent. Extensions that are not compatible re-enable the GIL.</p>
<h3 dir="ltr">Should I rewrite my Python backend in Rust?</h3>
<p dir="ltr">Profile first. Dropbox and Discord had specific reasons, and Instagram chose to tune Python instead.</p>
<h3 dir="ltr">Can I use both?</h3>
<p dir="ltr">Yes. PyO3 and maturin let you build Python packages with Rust cores.</p>
<h3 dir="ltr">Are TechEmpower benchmarks still maintained?</h3>
<p dir="ltr">The repository was archived in March 2026, and Round 23 from March 2025 was the last official round.</p>
<h2 dir="ltr"><strong>References and Sources</strong></h2>
<p dir="ltr">GitHub, &#8220;TechEmpower/FrameworkBenchmarks&#8221;: <a href="https://github.com/TechEmpower/FrameworkBenchmarks">https://github.com/TechEmpower/FrameworkBenchmarks</a></p>
<p dir="ltr">TechEmpower, &#8220;Framework Benchmarks Round 23&#8221;: <a href="https://www.techempower.com/blog/2025/03/17/framework-benchmarks-round-23/">https://www.techempower.com/blog/2025/03/17/framework-benchmarks-round-23/</a></p>
<p dir="ltr">Python.org, &#8220;PEP 779&#8221;: <a href="https://peps.python.org/pep-0779/">https://peps.python.org/pep-0779/</a></p>
<p dir="ltr">Python Docs, &#8220;What&#8217;s New In Python 3.14&#8221;: <a href="https://docs.python.org/3/whatsnew/3.14.html">https://docs.python.org/3/whatsnew/3.14.html</a></p>
<p dir="ltr">Python Docs, &#8220;Python support for free threading&#8221;: <a href="https://docs.python.org/3/howto/free-threading-python.html">https://docs.python.org/3/howto/free-threading-python.html</a></p>
<p dir="ltr">The Register, &#8220;Feature freeze for Python 3.15 as first beta released&#8221;: <a href="https://www.theregister.com/devops/2026/05/11/feature-freeze-for-python-315-as-first-beta-released/5237934">https://www.theregister.com/devops/2026/05/11/feature-freeze-for-python-315-as-first-beta-released/5237934</a></p>
<p dir="ltr">Stack Overflow, &#8220;2025 Developer Survey: Technology&#8221;: <a href="https://survey.stackoverflow.co/2025/technology">https://survey.stackoverflow.co/2025/technology</a></p>
<p dir="ltr">Discord, &#8220;Why Discord is switching from Go to Rust&#8221;: <a href="https://discord.com/blog/why-discord-is-switching-from-go-to-rust">https://discord.com/blog/why-discord-is-switching-from-go-to-rust</a></p>
<p dir="ltr">Cloudflare, &#8220;How we built Pingora, the proxy that connects Cloudflare to the Internet&#8221;: <a href="https://blog.cloudflare.com/how-we-built-pingora-the-proxy-that-connects-cloudflare-to-the-internet/">https://blog.cloudflare.com/how-we-built-pingora-the-proxy-that-connects-cloudflare-to-the-internet/</a></p>
<p dir="ltr">Dropbox Tech, &#8220;Rewriting the Heart of Our Sync Engine&#8221;: <a href="https://dropbox.tech/infrastructure/rewriting-the-heart-of-our-sync-engine">https://dropbox.tech/infrastructure/rewriting-the-heart-of-our-sync-engine</a></p>
<p dir="ltr">Instagram Engineering, &#8220;Dismissing Python Garbage Collection at Instagram&#8221;: <a href="https://instagram-engineering.com/dismissing-python-garbage-collection-at-instagram-4dca40b29172">https://instagram-engineering.com/dismissing-python-garbage-collection-at-instagram-4dca40b29172</a></p>
<p dir="ltr">Pydantic, &#8220;Pydantic V2 alpha&#8221;: <a href="https://pydantic.dev/articles/pydantic-v2-alpha">https://pydantic.dev/articles/pydantic-v2-alpha</a></p>
<p dir="ltr">PyO3, &#8220;PyO3 user guide&#8221;: <a href="https://pyo3.rs/">https://pyo3.rs/</a></p>
<p dir="ltr">Rust Blog, &#8220;2025 State of Rust Survey Results&#8221;: <a href="https://blog.rust-lang.org/2026/03/02/2025-State-Of-Rust-Survey-results">https://blog.rust-lang.org/2026/03/02/2025-State-Of-Rust-Survey-results</a></p>

Python vs Rust for High-Performance Backend Architecture in 2026
Python vs Rust for High-Performance Backend Architecture in 2026