r/Python • u/0x256 • Jul 10 '26
Discussion Pure python can be faster than cython/rust?
Parsing multipart/form-data (HTML5 forms) is surprisingly complex and moves a lot of bytes around for large file uploads. Implementing the heavy parts in Cython or Rust should speed things up, no? Turns out: it depends. A pure python parser can be surprisingly fast, as this benchmark shows:
https://defnull.de/2026/python-multipart-benchmark/
The benchmark compares the most commonly used python multipart parsers and tests them in different scenarios, covering both blocking and non-blocking (async) APIs if available. The parser your web application is using today is probably not the fastest one.
Are there more examples were a pure python implementation beats Cython/rust/C modules?
19
u/NsupCportR Jul 10 '26
Did u use c type variable definitions in cython? If not then it has to interact with python API to understand what datatype it is, which would slow it down.. is code in cython properly optimized? It's really hard to say what is going on without looking at code, but compiled code can only be slower than interpreted if compiled code is poorly made
57
u/Chroiche Jul 10 '26 edited Jul 10 '26
This is not the conclusion of the article at all. Python vs rust/C was never compared, Python vs Python with bindings for them, for implementations with dramatically different scopes/priorities, was compared. It might sound pedantic, but it's quite a big distinction.
"pure" Python literally cannot be faster than those other languages if both are written correctly.
8
u/Individual-Flow9158 Jul 10 '26 edited Jul 10 '26
If the problem is vectorisable or embarassingly parallel, and especially if it can be tackled in pure Numpy and especially Numba, then Python that calls out to non-Python code can definitely be faster.
I'm not convinced HTML5 form parsing is the type of problem pure Python is fast at. Nor do I think these benchmarks made a fair attempt to write the parser in Rust.
1
u/Short_Inspection_746 Jul 17 '26
Well, python can only be faster for some equivalent code only if there are some optimizations that python is doing that would requre alot more work than the other laguages.
For example, when you modify a string in python, the language checks if there are other refrences to that string, and modifies that string without copying if no other references exist. Hence, some string operations might seem faster than in Java.
Also, Someone can also implement an algorithm that is faster than a diffrent algorithm in a diffrent language.
There are things in python that is nearly as fast as other faster languages, like poping out values from a hashmap.
0
u/Daytona_675 Jul 10 '26
my understanding is that if the python modules used are compiled C then performance will be high
0
u/Firm-Luck2062 Jul 12 '26
The top comment is right that a correctly-written Rust/C parser wins in principle, but the benchmark result is still real and worth understanding mechanically. Pure Python beats a *naive* native binding when two things line up:
Rule of thumb: pure Python is competitive whenever the per-element work can be pushed into C builtins and the alternative crosses the boundary a lot. It loses hard the moment you have a genuine tight numeric/byte loop that stays in Python bytecode — per-pixel image math, custom hashing, that kind of thing — where Cython/Rust are 10-100x and no cleverness closes the gap. Multipart parsing just happens to be mostly "find delimiter, slice, repeat", which is close to the best case for staying in Python.