I think you may split the async endpoints and the sync endpoints into two
different procress group and start them in different ways( different start
up command, worker and different port). And config the Load Balancer
(Nginx?) to point to different ports by path..
I would handle the migration
I know you can run gunicorn with uvicorn workers. But the sync views will
be running sync, no longer gevent patched, meaning performance could
change. I’m also unsure if sync views are serialized into one thread if you
don’t set DJANGO_ALLOW_ASYNC_UNSAFE, which could be a bottleneck.
I did
Thanks
On Mon, 17 Apr 2023, 11:42 am Fortune Osho, wrote:
> You can simply run gunicorn with unicorn workers... which is very
> performance using uvloop... test it performance against pure gunicorn...
> note that performance is not totally dependent on server used(a whole lot
> of things can
You can simply run gunicorn with unicorn workers... which is very
performance using uvloop... test it performance against pure gunicorn...
note that performance is not totally dependent on server used(a whole lot
of things can affect performance like moddlewares, serialization etc)
On Sun, Apr
Hello
Production django app, currently 100% sync views, running under gunicorn
with gevent worker class.
@andrewgodwin suggests here it is possible to migrate slowly, just run
hybrid sync-async and add or convert views as desired
https://www.youtube.com/watch?v=19Uh_PA_8Rc=1728s
But to get a
5 matches
Mail list logo
