Skip to content
Hallway
0:00 / 0:00

#latency#hdrhistogram#benchmarking

Understanding Latency & Application Responsiveness

Parleys

15K subscribers • 3 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Presented by Gil Tene, CTO and co-founder of Azul Systems

Advanced. Deep dive for people who know the field.

2.3K views10 years ago1 recommendation

Systems programmingDistributed systemsPerformance and optimizationObservability and monitoring

Gil Tene explains the methodologies for measuring, reporting, and investigating latencies, highlighting common pitfalls in performance benchmarking.

Managing, monitoring, and improving application responsiveness is a common need for many software professionals. Whether you develop applications or manage them, understanding application responsiveness and the major mechanisms that affect it is key to achieving successful applications and happy users. In this session, Gil Tene will provide a an in-depth overview of Latency and Response Time Characterization, including proven methodologies for measuring, reporting, and investigating latencies, and and overview of some common pitfalls encountered (far too often) in the field. Author: Gil Tene Gil Tene is CTO and co-founder of Azul Systems. He has been involved with virtual machine and runtime technologies for the past 25 years. His pet focus areas include system responsiveness and latency behavior. Gil is a frequent speaker at technology conferences worldwide, and an official JavaOne Rock Star. He pioneered the Continuously Concurrent Compacting Collector (C4) that powers Azul's continuously responsive Java platforms. In past lives, he also designed and built operating systems, network switches, firewalls, and laser based mosquito interception systems. @giltene

Why it's here

1 person recommends this

What people say. Recommended as a definitive deep dive into properly measuring and comparing latency and application responsiveness.

u/plokhotnyukin r/scala • Recommends

On “A question about Http4s new major version”

*Main:* Probably in the htt4s Discord channel you will receive the answer faster. *Bonus:* On contemporary servers http4s is able to handle more than 130K tiny HTTP 1.1 requests per second reusing opened connections. You can use async-profiler to see on its interactive flame graph reports what is happening under the hood (where CPU cycles are spent, where allocations are happening, etc.). Please take in account that max RPS depends on the request service time and number of queued requests in the server memory (see Little's Low). Also, it is limited by different scalability limits (see Universal Scalability Law). For example if your server has the max allocation rate 12Gb/s and when h…
19View on Reddit

u/plokhotnyukin r/scala • Recommends

On “Benchmarking costs of running different langs/ecosystems”

…choosing secure and scalable technology from the start can supercharge your ability to expand services and captivate a large audience with ease. If you're into optimizing web app performance and scalability, check out this fantastic deep-dive presentation by Gil Tene (the genius behind HdrHistogram, wrk2, and other killer libraries and tools): [video It's all about properly measuring and comparing latency/responsiveness in applications and why it is matter for business (on the same level with security and correctness). Threw in async-profiler to peek under the hood and uncover bottlenecks in CPU cycles, allocations, or any other \`perf\` tool metric. Currently, async-profiler support…
6View on Reddit