[LU-3184] link max_rpcs_in_flight to peer credits Created: 17/Apr/13 Updated: 21/Feb/16 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.5.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 7772 |
| Description |
|
[Andreas writing with James' account] The client max_rpcs_in_flight parameter is often tuned to try and get better performance from clients with large bandwidth-delay products. Unfortunately, people are less familiar with tuning the LNET peer credits values, and this results in the Lustre layer trying to send RPCs concurrently that will never go on the wire at the same time. It would make sense to increase the LNET peer credits when the max_rpcs_in_flight is increased above the current value, so that users get the behaviour that they expect. |
| Comments |
| Comment by Isaac Huang (Inactive) [ 30/Apr/13 ] |
|
I don't think they can be linked:
|
| Comment by Cory Spitz [ 30/Apr/13 ] |
|
You might not be able to tie max_rpcs_in_flight to ni credits either, but it would be easier than peer_credits alone. Maybe this just turns into an LUDOC bug where the guidance on tuning is updated then? What are your thoughts about linking (in some way, not necessarily rigidly) max_rpcs_in_flight and max_dirty_mb? |
| Comment by Andreas Dilger [ 24/Oct/14 ] |
|
If you don't think that there should be a link in the code between max_rpcs_in_flight and peer credits/NI credits, could you please submit a patch to the Lustre User Manual to link places that discuss tuning max_rpcs_in_flight to the relevant sections that describe tuning peer credits/NI credits, and how they interact. I still see many places where people advocate increasing max_rpcs_in_flight, but this may not help if there are not enough peer credits. |