0 views collected around this technical thread.
This article reviews various techniques for detecting network latency at each TCP/IP layer, including application‑layer tools like Telnet, transport‑layer utilities such as TCPPing, UDPPing and Tcproute, network‑layer protocols like ICMP with Ping and Tracert, and hardware‑based measurements at the link layer.
Client‑side developers can boost API speed and user experience by collaborating with back‑end teams to cut server processing and network latency, using caching, concurrency, smaller or UDP‑based packets, and aggressively pruning or compressing payloads, which can shrink megabyte responses to tens of kilobytes and shave dozens of milliseconds off latency.
This article explains the TCP slow‑start algorithm, how its initial 10‑packet window translates to a practical 14 KB rule for web pages, and why keeping the first‑byte payload under this size dramatically reduces latency across various network conditions.
This article explains how to identify the root causes of increased network latency on Linux servers, covering tools such as ping, traceroute, hping3, and wrk, demonstrating packet analysis with tcpdump and Wireshark, and showing how TCP delayed ACK and socket options affect response times.
This article explains how to identify the root causes of Linux network latency—such as slow transmission, kernel processing, and application delays—by using tools like ping, traceroute, hping3, wrk, tcpdump, and Wireshark, and demonstrates practical testing with Nginx containers to analyze and mitigate latency issues.
This article presents a systematic performance test of the DTLE data replication tool, using sysbench, tc, and iperf3 to simulate different network latency and bandwidth scenarios, and compares DTLE's replication delay and bandwidth usage against native MySQL replication across three test cases.
This article provides a detailed quantitative analysis of TCP connection establishment latency, examining normal handshake processes, abnormal scenarios like queue overflows and TIME_WAIT exhaustion, and offering practical optimization strategies for backend systems.
This article investigates how the MySQL 8.0 group_replication_member_expel_timeout parameter influences node expulsion in a group replication cluster when network latency is introduced, describing the test environment, methodology, commands, observations, and configuration recommendations.
The article explains that game servers, especially real‑time multiplayer titles, avoid microservices because the added network overhead, stateful communication requirements, and strict latency constraints make monolithic or tightly coupled designs more suitable for high‑performance gameplay.
While 5G’s radio link can reach about 1 ms, true end‑to‑end latency remains dominated by core and internet delays, so 4G, 5G‑NSA and 5G‑SA differ only modestly; however, combining 5G Standalone with Multi‑access Edge Computing can cut total latency below 10 ms, enabling ultra‑reliable low‑latency applications.
This article explains how to assess, monitor, and tune system I/O performance by defining I/O models, selecting appropriate evaluation tools, tracking key metrics for disk and network I/O, and applying practical optimization strategies for both storage and network bottlenecks.
This article explains how to assess and improve system I/O performance by defining I/O models, selecting appropriate evaluation tools for disk and network, monitoring key metrics such as IOPS, bandwidth and latency, and applying host, network, and storage‑side optimization techniques for high‑throughput and low‑latency workloads.
The article argues that cold backup and active‑passive setups provide false security and outlines how true active‑active disaster‑recovery requires local‑datacenter request handling, business‑driven data sharding, and low‑latency cross‑site synchronization, recommending a staged rollout from city‑level to cross‑region architectures while weighing ROI.
This article explains how to assess I/O capabilities, choose appropriate evaluation tools, monitor key performance metrics, and apply targeted optimization techniques for both disk and network I/O to improve system throughput and latency.
This article presents a comprehensive, data‑driven guide to reducing latency and increasing throughput of Nginx‑based web servers by covering hardware selection, low‑level OS tuning, network‑stack adjustments, TLS optimizations, and application‑level configurations, all illustrated with real‑world Dropbox experience.
The article explains that traditional CDNs deliver limited performance gains for mobile users because the dominant last‑mile latency of wireless networks overshadows CDN benefits, and it explores data, misconceptions, cost considerations, and possible strategies for improving mobile content delivery.
The article analyzes Ilya Grigorik's findings that traditional CDNs deliver minimal performance gains for mobile users due to high last‑mile latency, outlines latency components, presents comparative data, and discusses the operational challenges of deploying mobile‑optimized edge caching.