A space to discuss and keep up software development and manage your software career
An inclusive community for gaming enthusiasts
News and discussion of science and technology such as AI, VR, cryptocurrency, quantum computing, and more.
From composing and gigging to gear, hot music takes, and everything in between.
Memes and software development shitposting
Discussing AI software development, and showing off what we're building.
Movie and TV enthusiasm, criticism and everything in-between.
Web design, graphic design and everything in-between
A community for makers, hobbyists, and professionals to discuss Arduino, Raspberry Pi, 3D printing, and much more.
For engineers building software at scale. We discuss architecture, cloud-native, and SRE—the hard-won lessons you can't just Google
Discussing the core forem open source software project — features, bugs, performance, self-hosting.
A collaborative community for all things Crypto—from Bitcoin to protocol development and DeFi to NFTs and market analysis.
At this stage, Django Channels ( WebSocket support ) is more matured and can able to use in production.
Django Channels work, but the performance just isn't great. It's a good fit if your app is small. If it grows you'll want to use C++, Java, Elixir or Golang (my favorite) for websockets in order to be cost effective.
What benchmarks are you using to determine the performance evaluation?
True, synchronous code running on an internal thread executor on an event loop will be slower than fully async, but still curious.
And which version of channels did you try most recently?
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
At this stage, Django Channels ( WebSocket support ) is more matured and can able to use in production.
Django Channels work, but the performance just isn't great. It's a good fit if your app is small. If it grows you'll want to use C++, Java, Elixir or Golang (my favorite) for websockets in order to be cost effective.
What benchmarks are you using to determine the performance evaluation?
True, synchronous code running on an internal thread executor on an event loop will be slower than fully async, but still curious.
And which version of channels did you try most recently?