On Fri, 1 Jul 2022 at 19:23, Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> wrote: > 2) Define QoS policies for the connections using the kernel Traffic If it helps, we use HTB qdisc/classes on our Linux NFS servers to optionally limit the total egress and ingress (ifb) bandwidth to/from our renderfarm. User workstations are exempt from these limits so always get full speed. We can do this fairly easily because our network is well defined and split into subnet ranges so filtering by these allows us to differentiate between host classes (farm/workstations etc). Strictly speaking, it's a bit more complicated in that we only apply limits and change them dynamically based on the "load" of the server and how well it is keeping up with demand. This is just a bash script running in a loop looking at the state, scaling the HTB limits and applying filters. Our goal is to always ensure that taff have a good experience on their interactive desktops and we'll happily slow batch farm jobs to keep it that way. It is basically a low-pass filter that limits server load spikes. To do something similar by user or process, you could run your jobs in a cgroup and have it mark the packets that the server could then use to filter. But I think this only works for the client writes to the server as you have no way to mark and act on the egress packets out of the server? Daire
