SMB2 server is ungenerous with its credits
The initial number of credits we during session setup (with #11784 applied) is 20 and the maximum a client can hold is 1000. This seems a bit low. On Windows the initial number of credits returned is 512 and the maximum is 8192.
Updated by Gordon Ross over 1 year ago
- Status changed from New to Feedback
A client should only need enough credits to keep your I/O subsystem busy. Credits (more or less) represent the number of current I/O request that client may have. Once you have enough I/O running to keep your filesystem busy, having more credits does not help (and is likely another case of "buffer bloat"). Can you show that it makes a significant difference in performance to allow a single client to run so many concurrent I/O requests?