3 ms·
Curious to see how this fares against something like uWSGI with aiohttp support (haven't tried either, but uWSGI brings so much more to the table than speed tha
by rcarmo 10y ago
Curious to see how this fares against something like uWSGI with aiohttp support (haven't tried either, but uWSGI brings so much more to the table than speed that I'd like to be able to make an informed choice).
- ddorian43 10y agoasyncio is experimental still on uwsgi http://uwsgi-docs.readthedocs.io/en/latest/asyncio.html http://uwsgi-docs.readthedocs.io/en/latest/asyncio.html
- rcarmo 10y agoWhich is why I haven't tried it yet. :)
- dom0 10y agoRunning asyncio-based servers on uwsgi is very stable though, but may not achieve 100 % of the performance native asyncio in uWSGI may have. Even then, Tornado is "fast enough" for us (ie. we run out of network bandwidth before we run out of CPU). But the main advantage - that you're still using uwsgi as a "unified application server" of sorts - persists, which was the main point for us (Django, Flask, Tornado on uWSGI). This simplified deployment and administration quite a bit. Re. topic: It would be really interesting to see it compared to Tornado.
- rcarmo 10y agoYeah, I use uWSGI for a lot of things (check out http://github.com/rcarmo/piku http://github.com/rcarmo/piku, for instance), so am more interested in figuring out if I can get a little extra mileage off it.