Skip to content
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

Consider merging aio and task frameworks #1334

Open
gdamore opened this issue Nov 10, 2020 · 1 comment
Open

Consider merging aio and task frameworks #1334

gdamore opened this issue Nov 10, 2020 · 1 comment

Comments

@gdamore
Copy link
Contributor

gdamore commented Nov 10, 2020

Originally we had the idea of a general purpose task framework, and that the aio framework could make use of it. However this separation has complicated things a bit, and it would be easier to follow the flows, if we had the entirety of the task framework in the aio framework.

This might allow us to reduce some of the hot locks as well, and in particular I want to break up the aio_lk.

@gdamore gdamore added this to the v1.5 milestone Jan 17, 2021
@gdamore gdamore removed this from the v1.5 milestone Jan 2, 2025
@gdamore
Copy link
Contributor Author

gdamore commented Jan 2, 2025

This is something I'd still like to do, but its tricky to do it, and still obtain any performance benefit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant