[21-23]
6[24-27] 7[28-31]" # same as cpu_npartition=8
or even more complex distribution, see Lustre Manual for details.
Also check "lctl get_param cpu_partition_table" to see your current partition
table.
Aurélien
De : lustre-discuss de la
On May 2, 2024, at 18:10, Anna Fuchs
mailto:anna.fu...@uni-hamburg.de>> wrote:
The number of ptlrpc threads per CPT is set by the "ptlrpcd_partner_group_size"
module parameter, and defaults to 2 threads per CPT, IIRC. I don't think that
clients dynamically start/stop ptlrpcd threads at
The number of ptlrpc threads per CPT is set by the
"ptlrpcd_partner_group_size" module parameter, and defaults to 2
threads per CPT, IIRC. I don't think that clients dynamically
start/stop ptlrpcd threads at runtime.
When there are RPCs in the queue for any ptlrpcd it will be woken up
and
On Apr 29, 2024, at 02:36, Anna Fuchs
mailto:anna.fu...@uni-hamburg.de>> wrote:
Hi Andreas.
Thank you very much, that helps a lot.
Sorry for the confusion, I primarily meant the client. The servers rarely have
to compete with anything else for CPU resources I guess.
The mechanism to start new
Hi Andreas.
Thank you very much, that helps a lot.
Sorry for the confusion, I primarily meant the client. The servers
rarely have to compete with anything else for CPU resources I guess.
The mechanism to start new threads is relatively simple. Before a
server thread is processing a new
On Apr 28, 2024, at 16:54, Anna Fuchs via lustre-discuss
mailto:lustre-discuss@lists.lustre.org>> wrote:
The setting max_rpcs_in_flight affects, among other things, how many threads
can be spawned simultaneously for processing the RPCs, right?
The {osc,mdc}.*.max_rpcs_in_flight are actually
Hello everyone.
The setting |max_rpcs_in_flight| affects, among other things, how many
threads can be spawned simultaneously for processing the RPCs, right?
In tests where the network is clearly a bottleneck, this setting has
almost no effect - the network cannot keep up with processing the
