-
Notifications
You must be signed in to change notification settings - Fork 11
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
Expose MaxConnsPerNode from AeroSpike to allow easier performance tuning #187
Expose MaxConnsPerNode from AeroSpike to allow easier performance tuning #187
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rubber stamp - would need another reviewer to review it before merging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Description
This PR is to expose MaxConnsPerNode from AeroSpike to allow easier performance tuning.
Note 1: We leave
MaxConnsPerNode
as 100 which is the default from Aerospike. However, Aerospike has also updated other default settings, see the change reasons from Aerospike forum. We will update AsyncMaxCommands to 100 when we bump up Aerospike version so we align with Aerospike settings. Also, the relationship between asyncMaxConnsPerNode and MaxConnsPerNode can be found from here.Note 2: We are running into code cov issue and it seems that we didn't have token setup properly for this repo. I was instructed to comment out the code cov temporarily.
Type of Change
Checklist