How do you measure network and application latency?A “QoS Agent” deployed nearby the connected equipment or application uses an active monitoring approach i.e. it transfers small data payloads using multiple-protocols with a target. We calculate precise timestamps and send results to analysis. Which protocols are you using to measure latency?We use the classic ICMP but found that the results are less and less accurate due to network complexity/layers/priorities. Hence, we also use TWAMP for network level latency evaluations. But no applications will ever use these protocols hence we also measure using TCP, UDP and HTTP/S/3 and Industrial protocols such as Profinet and soon Scada and Modbus.Can the solution measure other quality metrics ?Yes. It also measures Bandwidth using iPerf3 and our own special energy efficient throughput measurement protocol, Jitter and Packet Loss.What data volume does your solution use to monitor latency?About 2Mb per day or 50Mb per month using typical parameters enabling multiple measurements per minute and per protocol. The big data usage comes from bandwidth measurements hence shall be done less often when using iPerf.How to you create dynamic latency heat maps ?When available, we can collect GPS data and associate it with latency measurements. This can be done using our mobile app or using our Contextual Agent. The heat map is a great tool to identify latency weak spots.
Can I deploy multiple QoS Agents and Reflectors ?Yes, is it possible to use multiple pairs of QoS agents – Reflectors to track quality and latency if multiple network paths. Furthermore, multiple QoS Agents can connect with the same Reflector. Multiple deployments can offer a segmented view facilitating real-time assessments of the connectivity performance.How can you assess the stability of the network latency ? First, we aggregate protocol-based measurements to form real-time indicators for network and application latency. Second, we calculate the latency volatility and using other indicators and data, we compute a “Latency Stability” indicator in %. You can then set thresholds and get alarms when stability is below expectations.How easy is it to install?It’s quick and easy as the solution is based on software containers and installation scripts. We also have support for Kubernetes and OpenShift. Most time may be spent on deciding where to locate the QoS Agents and Reflectors that is pertinent to your use case and setup the supporting hosts.Why focus on latency versus bandwidth when assessing connectivity performance?Both are important BUT many new services, like autonomous cars and robotaxis, teleoperation of remote equipment, portable medical devices, require ** stable low-latency and real-time ** connectivity to function properly, if latency varies too much, those services can quickly become unusable or even dangerous.How can I try LatenceTech’s solution to support a time-critical use case ?Check our Lab / Trial package or contact us to discuss details.