-
Notifications
You must be signed in to change notification settings - Fork 120
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
Performance optimization #153
Comments
At this point, |
We are no longer using NBD and switched back to NFS for our use case. |
However, the issue still exists, and I do still want to keep it on my radar, so reopening. |
How does nbd manage processes and threads? I am looking into this to find out what optimizations may be required and what settings to watch for as I start to use nbd-server more. Is there anything I need to watch out for when it comes to performance?
Is there a limit to the number of processes that are started? Is there a way to manage the number of processes?
The man page describes that the nbd-server will read requests in a main thread and handle those requests in separate threads. It appears, in my test environment, that a new process is always started when needed, as a client connects.
What is the correct way to get the number of threads?
When I set max_threads to 30, threads always stays at 1. I am checking this with
cat /prod/<nbd process id>/status | grep Thread
. Does the fact that I am making read-only requests to the server have something to do with this?My environment
(for context)
Thank you in advance for your help.
L
The text was updated successfully, but these errors were encountered: