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.

Sign up for GitHub

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

Jump to bottom

Reduce atomic contention for global activity count #898

Closed
msimberg opened this issue Dec 13, 2023 · 1 comment
Closed

Reduce atomic contention for global activity count #898

msimberg opened this issue Dec 13, 2023 · 1 comment
Assignees
@msimberg
Labels
effort: 3 A few days of work. priority: high This is essential functionality or a serious bug. Not addressing this blocks progress. type: refactoring

Comments

@msimberg
Copy link
Contributor

#704 added a global activity count to accurately detect when the runtime can safely be shut down. On x86 systems this seems to have had minimal impact on performance. On ARM (Grace) this seems to be noticeably more expensive. Investigate ways of reducing contention on the atomic count.
@msimberg msimberg added effort: 3 A few days of work. priority: high This is essential functionality or a serious bug. Not addressing this blocks progress. type: refactoring labels Dec 13, 2023
@msimberg msimberg added this to the 0.22.0 milestone Dec 13, 2023
@msimberg msimberg moved this from Backlog to Todo in pika planning board Dec 18, 2023
@msimberg msimberg self-assigned this Jan 11, 2024
@msimberg msimberg moved this from Todo to In Progress in pika planning board Jan 11, 2024
@msimberg msimberg removed this from the 0.22.0 milestone Jan 12, 2024
@msimberg
Copy link
Contributor Author

This doesn't seem to be as much of a problem I thought it was. E.g. #923 and #927 are far more important for improving performance.

@msimberg msimberg closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in pika planning board Jan 12, 2024
@msimberg msimberg moved this from Done to Archive in pika planning board Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@msimberg msimberg

Labels
effort: 3 A few days of work. priority: high This is essential functionality or a serious bug. Not addressing this blocks progress. type: refactoring
Projects
pika planning board
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msimberg