18
What async really means for your python web app? (hackeryarn.com)
submitted 10 months ago by to c/python@programming.dev
10 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 10 months ago (7 children)

Wow, very interesting to see Sync doing so well in comparison!

But I thought a lot of the advantage of async is it's ability to handle many concurrent requests? What happens if you run the same tests but this time with 100 requests in parallel?

  • permalink
  • fedilink
  • source
  • hideshow 7 child comments
    •
  • [–] 2 points 10 months ago (2 children)

    I've run python progs with 1000+ threads and it's fine. 10k might be harder. Async is overrated. Erlang and elixir are preferable.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 10 months ago

    overrated or not the choice is between sync or async drivers. Actually there is no choice, just an illusion of choice.

    So async or async ... choose. Without the web router running multithreaded, concurrency will have minimal effect. But everything is step by step. freethreaded hasn't been out for very long.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 10 months ago (1 child)

    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...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 10 months 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.

  • permalink
  • fedilink
  • source
  • parent