5 ms·

Uvloop – Ultra fast implementation of asyncio event loop on top of libuv

• 1st1 10y ago
  Pleased to see a uvloop link here again ;) I'm the author, feel free to ask questions. I also recommend to read our blog posts about uvloop and asyncio on magic.io
  • millisecond 10y ago
    Looks great! Is it possible / in the works to port back to 2.x?
    • 1st1 10y ago
      uvloop is meant to work with asyncio, which requires Python 3. So there is no point in supporting Python 2 (and trollius isn't maintained anymore).
      • millisecond 10y ago
        Ah, makes sense. Relatively new to Python world and getting a handle on all the version differences.
        • scrollaway 10y ago
          Unless there's a particular software or environment you're using that only supports Python 2, you'll want to deal with Python 3.4 at least.
  • giaosudau 10y ago
    Do you guys have any plan to support porting from Django/Flask to Uvloop? If I have a plan to develop a web api base on Uvloop how do I start?
    • 1st1 10y ago
      > Do you guys have any plan to support porting from Django/Flask to Uvloop? I don't think it makes a lot of sense to run Django/Flask on top of uvloop--the performance benefits will be negligible, if any. > If I have a plan to develop a web api base on Uvloop how do I start? In a few months we plan to opensource a web micro-framework based on uvloop & httptools. Right now you can use aiohttp which is quite mature.
      • Jcol1 10y ago
        Can you share in general how it improves over aiohttp (speed, architecture etc)
        • nerdwaller 10y ago
          Aiohttp is the next layer up the stack, it just utilizes whichever event loop policy is active. So basically it just makes it faster in most (all?) async things it does. I use aiohttp and uvloop fairly heavily, though I've not formally benched with/without uvloop in quite some time.
    • opticalfiber 10y ago
      Neither Django nor Flask is asynchronous/event loop based. It would neither make sense nor improve performance to run a Django/Flask app on top of uvloop. If you want to develop a web API using uvloop, you should look at aiohttp (http://aiohttp.readthedocs.io/en/stable/ http://aiohttp.readthedocs.io/en/stable/).
      • eeZi 10y ago
        Or Tornado, which migrated to the asyncio event loop and is a much more mature alternative.
  • dpraburaj 10y ago
    I have some questions related to the usage of async. At what scale(in terms of number of users or server load) would choosing async based web frameworks over traditional web frameworks like Django/Pylons make sense? While using async is much easier with the new async/await syntax compared to traditional async solutions like twisted, tornado etc., a lot of popular database connectors and ORMs do not support async currently. Even if the libraries a person needs are present at the moment, there's always the chance that a library maybe required in the future that does not support async and it may not be feasible to write a replacement(either due to the person's lack of expertise or due to lack of funds to hire someone else to write it). In such a case, would using a traditional library by spawning threads to run any blocking operation be a good stop-gap solution(until an async replacement comes along)?
    • inglor 10y ago
      In general, mixing synchronous and asynchronous I/O typically brings you the worst in both worlds. This has been a nightmare in C# which pioneered async/await - a lot of developers are struggling with footguns from mixing sync and async code. Ryan Dhal said that he picked JavaScript for Node because he was afraid of this and wanted a language without synchronous APIs already built in. I think Python 3.5+ async/await is fantastic don't get me wrong - but if you want to mix and match I'd recommend getting a second server that runs the synchronous framework and then communicating over network (REST HTTP for example) between the completely asynchronous server and the one running the thread pool.
      • aikah 10y ago
        > This has been a nightmare in C# which pioneered async/await - a lot of developers are struggling with footguns from mixing sync and async code. The big difference is that C# supports both multithreading and parallelism out of the box. Python has multithreading but with a GIL, nodejs has none of the 2.
    • 1st1 10y ago
      > At what scale(in terms of number of users or server load) would choosing async based web frameworks over traditional web frameworks like Django/Pylons make sense? Using async makes sense where you want to handle 100s/1000s of long-open connections (websockets for instance). Spawning a lot of threads/processes can be very expensive, and will lead to suboptimal QoS. > While using async is much easier with the new async/await syntax compared to traditional async solutions like twisted, tornado etc., a lot of popular database connectors and ORMs do not support async currently. Good news is that you can have most of your application written in Django (or other traditional web framework), using async to implement specific API endpoints.
  • nerdponx 10y ago
    What are the possible downsides to using uvloop?
    • 1st1 10y ago
      As far as I know, the only issue is that we don't support Windows atm. Which in most cases is fine -- you can develop on windows using vanilla asyncio, and use uvloop when deploying on *nix.
    • nerdwaller 10y ago
      As a heavy user of asyncio and uvloop, I haven't found any downsides yet (well, other than no windows support if you're on windows). Async Python takes a little learning, but generally speaking I think it's one of the cleanest implementations of async programming to date.
• jmunsch 10y ago
  What are the benchmarks as compared to curio? Are there any benefits to using uvloop vs curio?