I wonder about the end-result payoff of this approach. In general,
Django/Python code is not going to be I/O bound, which is where
asynchronous approaches are going to get the bang for your buck. Even when
it comes to DB access—the DB is a lot faster than the python and django
code running agai
On Fri, Jun 7, 2019 at 9:19 AM John Obelenus wrote:
> I wonder about the end-result payoff of this approach. In general,
> Django/Python code is not going to be I/O bound, which is where
> asynchronous approaches are going to get the bang for your buck. Even when
> it comes to DB access—the DB is