James Addison, I also currently use `psycogreen.gevent` for postgresql async behaviour. >
How did you go about using psycogreen.gevent for async postgres? I tried using various tools and was unsuccessful in seeing any performance improvements. I was following the info here: https://medium.com/@bfirsh/squeezing-every-drop-of-performance-out-of-a-django-app-on-heroku-4b5b1e5a3d44 Have any suggestions/tips? django blocking while waiting for postgres is a huge bottleneck for my app. Thanks! How did you go about using psycogreen.gevent for postgresql async behavior? I'm On Tuesday, August 21, 2018 at 10:16:03 AM UTC-7, James Addison wrote: > > On Monday, June 4, 2018 at 6:18:23 AM UTC-7, Andrew Godwin wrote: >> >> For a while now I have been working on potential plans for making Django >> async-capable, and I finally have a plan I am reasonably happy with and >> which I think we can actually do. >> > > Andrew, > > Out of curiosity, how would these kinds of changes interact with gunicorn > running with a `gevent` worker? I also currently use `psycogreen.gevent` > for postgresql async behaviour. > > Thanks, > James > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/3f676d11-7b2c-41f7-a19f-d34f3b0a1b50%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
