this post was submitted on 31 Dec 2025
19 points (88.0% liked)

Python

7727 readers
52 users here now

Welcome to the Python community on the programming.dev Lemmy instance!

๐Ÿ“… Events

PastNovember 2023

October 2023

July 2023

August 2023

September 2023

๐Ÿ Python project:
๐Ÿ’“ Python Community:
โœจ Python Ecosystem:
๐ŸŒŒ Fediverse
Communities
Projects
Feeds

founded 2 years ago
MODERATORS
erlingur@programming.dev
jnovinger@programming.dev
norambna@programming.dev
19
What async really means for your python web app? (hackeryarn.com)
submitted 1 month ago by hackeryarn@lemmy.world to c/python@programming.dev
13 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Ephera@lemmy.ml 1 points 1 month ago (1 children)

I mean, it's a bit of a weird comparison to begin with. Web servers were always able to parallelize without async, because they'd just spawn a new thread per request. The real advantage of async is programs where working with threads isn't as trivial...

[โ€“] hackeryarn@lemmy.world 2 points 1 month ago

I totally agree with you. This article was really a response to a lot of hype around async web servers in Python.

I kind of knew what to expect, but wanted to throw real numbers against it. I was surprised to see a 10x slowdown with the async switch in Django.