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

Allow for configurable number of shards #30

Closed
wants to merge 1 commit into from

Conversation

sparrc
Copy link

@sparrc sparrc commented Jul 22, 2016

closes #17

allows for users to get a concurrent map with a configurable number of shards

made it an optional "list" so that the .New() call signature doesn't change.

I've also set SHARD_COUNT to be a constant. This could break people, but I think it's better for users not to be modifying globals to change the libraries behavior.

@redbaron
Copy link
Contributor

why it is not merged? It is an obvious improvement in usability

@eranchetz
Copy link
Contributor

@sparrc @redbaron After confilcts are resolved I will merge this as well

@sparrc
Copy link
Author

sparrc commented Aug 15, 2016

done :)

@sparrc
Copy link
Author

sparrc commented Sep 5, 2016

the merge conflicts are a bit beyond me....if anyone else wants to re-submit this change then feel free, I don't have time at the moment to resolve the conflicts

@sparrc sparrc closed this Sep 5, 2016
@eranchetz
Copy link
Contributor

@sparrc Thanks a lot for your assitance, I think that right now using a configurable number of shards might cause some issues, @redbaron pull requests address the issues but not completely.

I hope that in the future we can implement your code in concurrent map.

Once again, thanks for your ideas and implementations. 👍

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.

why is shard count fixed 32?
3 participants