Performance

Framework Benchmarks

Transparent, reproducible benchmarks comparing Pyxle against popular web frameworks. Every framework implements identical endpoints with the same logic.

Methodology

Tool

autocannon v8

Duration

12s per test

Connections

10 concurrent

Hardware

Apple M3 (8 cores)

All Python frameworks use uvicorn (single worker, ASGI) except Flask (gunicorn, 4 WSGI workers). Node.js frameworks use their default server. Pyxle runs in production mode via pyxle serve with full middleware stack. Database: SQLite with WAL mode, 1,000 pre-seeded rows. Source code (run it yourself)

Highlights

Key Takeaways

Fastest full-stack Python framework

Pyxle outperforms Django by 2.2x on average across all API benchmarks, while offering SSR, file-based routing, and server actions that neither Django nor Flask provides.

SSR performance on par with Next.js

Pyxle renders server-side pages at 1,100+ req/s with a persistent worker pool and bundle caching. The gap with Next.js is just 1.4x — remarkable for a Python + Node.js hybrid architecture.

Zero errors under heavy load

Across all tests at 100 concurrent connections, Pyxle maintained zero errors and zero timeouts. Production-grade stability is not optional.

1.8x faster than FastAPI on POST

Pyxle handles POST/form processing at 20,000+ req/s — nearly double FastAPI. Starlette's ASGI layer combined with Pyxle's lean middleware stack shines for request body processing.

SSR Performance

Server-Side Rendering: Pyxle vs Next.js

Pyxle is the only Python framework that renders React on the server. Its optimized worker pool with bundle caching delivers throughput comparable to Next.js — the industry standard.

ConnectionsPyxle (req/s)Next.js (req/s)Ratio
14411,3643.1x
51,0391,6451.6x
101,0401,6201.6x
501,1491,6591.4x
1001,1681,6181.4x
SSR renders the homepage with server-side data loading, React component rendering, and full HTML document assembly. Pyxle uses persistent Node.js worker pool with esbuild bundle caching. Next.js uses pre-compiled React Server Components.

API Benchmarks

Endpoint Performance Comparison

Each framework implements identical API endpoints. Pyxle runs its full middleware stack (SSR support, GZip compression, server actions). API-only frameworks run leaner stacks by design.

Form Submission (POST)

Parse JSON body, validate fields, return response. Measures request processing pipeline.

Pyxle
20,548
FastAPI
11,379
Flask
5,338
Django
3,478

JSON Serialization

Return a static JSON object. Measures pure framework and serialization overhead.

FastAPI
15,423
Pyxle
5,046
Flask
5,044
Django
3,592

Health Check

Minimal endpoint. Measures raw framework routing overhead.

FastAPI
15,237
Flask
5,088
Pyxle
4,770
Django
3,506

Single DB Query

Read one random row from SQLite. Measures framework + database access overhead.

FastAPI
3,290
Django
3,054
Pyxle
2,696
Flask
2,658

Multiple Queries (5)

Read 5 random rows from SQLite. Measures query loop performance.

FastAPI
2,802
Pyxle
2,428
Django
2,225
Flask
2,124

Multiple Queries (20)

Read 20 random rows from SQLite. Heavier database workload.

Flask
2,476
Pyxle
2,046
FastAPI
2,027
Django
864

Reading these results

Pyxle is a full-stack framework — every request passes through its SSR-ready middleware stack, GZip compression, and server action routing, even on API-only endpoints. Lightweight API frameworks like FastAPI and Flask skip that overhead entirely. For real-world applications, Pyxle's value is that you get SSR, server actions, and Python's ecosystem in a single framework — at competitive throughput.

Run the benchmarks yourself

All benchmark code is open source. Clone the repo, start the servers, and run the suite on your own hardware.

View benchmark source