---
answer: direct
beat: system-design
source: 1 article · updated: November 17, 2026
---

Why does payload compression trade CPU time for network time, and when is that worth it?

Compressing a response (gzip, brotli) costs CPU cycles on the server and decompression cycles on the client, in exchange for transmitting fewer bytes over the network. This is a clear win when network transfer time dominates the request's total latency — large payloads, slower or higher-latency connections — and a much smaller win, or even a net loss, for tiny payloads where compression overhead exceeds the bytes saved.

Answered in

5 API Performance Techniques That Actually Move the Needle

Pagination, async logging, caching, compression, and connection pooling — five concrete techniques that cut API latency without touching business logic.

Crashtech Editorial November 17, 2026 System Design & Architecture

Read the full analysis

Other questions this article answers

More system design & architecture questions

Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.