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

Better Understanding the PartitionCount Configuration #16

Open
jon-whit opened this issue Feb 24, 2021 · 1 comment
Open

Better Understanding the PartitionCount Configuration #16

jon-whit opened this issue Feb 24, 2021 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@jon-whit
Copy link

@buraksezer First of all, I want to say thanks for this awesome implementation! I've started to use it in one of my projects.

I did, however, have a question about the PartitionCount configuration. I haven't seen a lot of information in the literature about how this impacts the hashing and, more importantly, any strategies on how to best chose the value for any arbitrary type of query workload. What I'm trying to do is uniformly distribute queries for any given resourceID across N cluster members. I like this library because if one of the cluster members fails then the load is redistributed such that any one of the remaining members will receive <= (Load * 100 ) percent of the residual traffic.

But I don't quite yet understand how that goal relates with the PartitionCount, and if I choose a lower value such as 3, 5, or 9 then I experience issues with the library being able to distribute when I add more members. Your input/guidance would be appreciated :)

@buraksezer buraksezer self-assigned this Feb 25, 2021
@buraksezer buraksezer added the question Further information is requested label Feb 25, 2021
@jon-whit
Copy link
Author

@buraksezer any guidance on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants