As a simple rule of thumb, how much latency should be allowed per network switch hop?

The correct choice reflects a commonly accepted guideline in networking when assessing the latency that should be tolerated per network switch hop. Specifically, allowing 0.1 milliseconds of latency per switch hop helps maintain audio quality within a digital audio network.

When designing and implementing audio over Ethernet systems, especially with protocols like Dante, low latency is crucial for ensuring that there is minimal delay in audio signals, which is particularly important during live performances and real-time mixing situations. While the ideal scenario is minimizing latency as much as possible, allowing 0.1 milliseconds per switch hop strikes a balance between performance and the practical limitations of network hardware.

In systems where multiple switch hops are common, this figure helps engineers set realistic expectations and targets for audio clarity and synchronicity across devices. Higher latency figures associated with incorrect choices could negatively impact audio performance, as even small delays can lead to perceivable timing issues in musical applications. Therefore, adhering to this guideline ensures that the network can handle audio data efficiently while offering a satisfactory level of performance for professional audio applications.