Thanks to visit codestin.com
Credit goes to github.com

Skip to content

index: get rid of the locking #3558

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

Merged
merged 1 commit into from
Dec 28, 2015
Merged

index: get rid of the locking #3558

merged 1 commit into from
Dec 28, 2015

Conversation

carlosmn
Copy link
Member

We don't support using an index object from multiple threads at the same
time, so the locking doesn't have any effect when following the
rules. If not following the rules, things are going to break down
anyway.

@ethomson
Copy link
Member

I'll +1 the idea here. We make a pretty clear statement about threading and - presuming one follows that - this locking we do in the index is unnecessary at best. (At worst, we have not significantly tested this because it is wholly pointless given our stated threading model.)

We don't support using an index object from multiple threads at the same
time, so the locking doesn't have any effect when following the
rules. If not following the rules, things are going to break down
anyway.
@carlosmn
Copy link
Member Author

I'll just go ahead and merge it then, now that the tests pass.

carlosmn added a commit that referenced this pull request Dec 28, 2015
@carlosmn carlosmn merged commit a377648 into master Dec 28, 2015
@ethomson ethomson deleted the cmn/index-nolock branch January 9, 2019 10:26
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