[LU-17442] too many ldlm threads running on client with many cores Created: 18/Jan/24 Updated: 18/Jan/24 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.14.0, Lustre 2.16.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Andreas Dilger | Assignee: | WC Triage |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
Newer client nodes have up to 192 cores, and it is likely that more cores will appear in short order. The client runs 2-4 ldlm_cbCP_NN threads per CPT (32 for 192 cores), one ldlm_bl_NN thread per core, which is far too many since they are almost never active. It is unlikely that the client-side LDLM threads need to be per-CPT or per-core, and could instead have a fixed number of threads (e.g. sqrt(num_cores)) that are shared among all cores. |