4 ms·
Really excited about these efforts. Python is my main programming language, but for high volume endpoints it's sometimes necessary to switch to other languages.
by tschellenbach 10y ago
Really excited about these efforts. Python is my main programming language, but for high volume endpoints it's sometimes necessary to switch to other languages. In an ideal world I'd just use Python for everything. It will take a while before that's possible though. These performance gains don't mean much if your DB connection is still blocking.
How does your benchmark compare against GO, Elixir and Node?
- napperjabber 10y agoMagicStack has already taken the initiative. https://github.com/MagicStack/asyncpg https://github.com/MagicStack/asyncpg
- spamizbad 10y agoStill beta, but those postgres numbers are incredible. MagicStack is doing amazing things.
- mangeletti 10y agoExtrapolating from Techempower and from the OP's benchmarks, I got: 137% as many req/sec as Node 83% as many req/sec as Go I'm it sure where this goes when you factor in async IO, but my guess is that Node gains a little and Go loses a lot. When you add asyncpg to the mix my money is on Sanic winning by a long shot, in a benchmark that includes e.g., 3 queries and returning the results as JSON.
- mhuffman 10y agoI have found node and tornado to have practically identical performance. I have not had a lot of experience with GO and Elixir for web servers. nginx (openresty, really) has beat both of them them in all "normal" (ie. not limited by DB access, etc) usage conditions that I have tested.