A “hot path” is a code path that is perf-critical, either because it’s something that is really perf-intensive, or because it’s latency-sensitive. An example of the former is a long for loop, or large nested iteration that does some core computation and takes a long time. An example of the latter is the measure/layout/draw logic for your UI, which must be as fast as possible to avoid dropping frames. In general, these are code paths you want that to take the least amount of time possible, for one reason or another.

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

Sebastiano Poggi — seb@androiddev.social
Sebastiano Poggi — seb@androiddev.social

Written by Sebastiano Poggi — seb@androiddev.social

"It depends" 🤷‍♂️ - UXE on Android Studio at Google. A geek 🤓 who has a serious thing for good design ✨ and for emojis 🤟 Personal opinions only 😁

Responses (1)

Write a response