-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use uvloop where available #5374
Comments
interesting. We need this indeed to build our community of users. Given the facinating findings of our bug reporter. Let's edit the next 7.6 milestone. "Amazing stability" as the first keywords of that release. No big changes for now, perfect tuning like this. |
I would recommend to look into this once our application tester is stable again. Then we can more easily test for unexpected behaviour/edge cases. |
We will not include uvloop. Our network activity that requires high throughput has now been implemented in Rust. |
Moving to Asyncio enables us to use faster,
uvloop
reactor on those systems (Linux, Mac?) where available. Tests with Tribler exit nodes show thatuvloop
reduces CPU usage by 30% while also improving memory usage. This is especially important for low-tier platforms, such as ARM.Enabling it is a matter of literally two lines of code:
for systems with older
uvloop
version (e.g. Debian) orfor everything else.
The text was updated successfully, but these errors were encountered: