On Wed, Oct 7, 2020 at 6:57 AM Patrick Goetz <pgoetz@xxxxxxxxxxxxxxx> wrote:
> I don't see how sharing a TCP connection can result in a performance
> regression (the performance degradation of *not* sharing a TCP
> connection is why HTTP 1.x is being replaced), or how using different IP
> addresses on the same interface resolves anything. Does anyone have an
> explanation?
>
The two IPs give you a form of QoS. So, it's about performance isolation
across the mounts, not about improving the aggregate performance.
The example I mentioned was this one:
dd if=/dev/zero of=/mnt/mount1/zeros &
ls /mnt/mount2/
The writes to /mnt/mount1 keep the transport busy transmitting data. As
a result, the "ls" GETATTR (or whatever RPC) needs to wait on the
single transport, potentially for seconds. Putting the two mounts on
different IPs solves the problem, at least prior to trunking discovery.
