-
Notifications
You must be signed in to change notification settings - Fork 8
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
long waiting for get_volumes_by_pool request #29
Comments
we are using get_volumes_by_pool to find volumes by name |
As the CSI work and get retries due to timeouts from k8s the waiting time for the command can reach over 2.5m. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
our creation process takes a long time (about 45 sec, whereas in comparison it only takes about 5 sec via the SVC storage family)
we timed the get_volumes_by_pool command on dscli client vs pyds8k vs postman on pool with 240 vols and then on pool with 4 vols for comparison and fun.
results:
with 244 vols:
dscli client: 17s
pyds8k: 26s
postman: 24s
with 4 vols:
dscli client: 15s
pyds8k: 4.5s
postman: 4s
we can see that pyds8k is not giving us worst performance than the postman (which uses rest as well) so if there is a problem it's with the rest itself
The text was updated successfully, but these errors were encountered: