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

Avoid extra mutex contention #189

Merged
merged 3 commits into from
Aug 8, 2024

Conversation

albus522
Copy link
Contributor

@albus522 albus522 commented Aug 8, 2024

NOTE: This includes the commit from #188 so I didn't have to deal with wonky rebasing.

This limits the mutex lock to interactions with the stack that are small, fast, and atomic. Moving the connection close code outside the mutex as it doesn't impact the pool.

Sidenote: Thinking about releasing the reap update, it probably needs to be a major version bump as it breaks things for anyone that has used the defined extension points and interacts with @que. It is probably possible this could be modified to only introduce a breaking change if reap is used.

After max queue size connections have been reaped, no new connections are allowed to be created.
The connection shutdown block can safely happen outside the mutex. This allows another thread to safely grab a connection while the reaper is still working through old connections.
@mperham mperham merged commit 7d48bcb into mperham:main Aug 8, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants