liveBook · Manning

Resource utilization

As explained in Fast by Default

The amount of computing resources, such as memory, processor time, storage, or energy, consumed by software.

Resource utilization measures the computing resources software consumes, including CPU time, memory, storage, and energy. Treat it as a user-facing performance concern: excessive consumption interferes with multitasking, increases failure risk, and turns technical limits into business trade-offs. section 3.2.4 section 6.1

Manage resource utilization by:

  • Separating idle and active usage; desktop applications should remain below 1% CPU and 500MB memory when idle, then release resources when backgrounded. section 3.2.4
  • Tracking memory growth over days or weeks, because leaks become especially damaging when users leave applications running continuously. section 3.2.4
  • Measuring resource consumption alongside responsiveness, file-operation time, and complete user flows rather than optimizing isolated metrics. section 3.2.4 section 3.6
  • Converting goals into budgets with baselines, headroom, ownership, and regular review so additions expose explicit trade-offs. section 6.9

A desktop productivity application

An application that consumes 2GB of RAM or regularly maxes out a CPU core disrupts other work. Measure idle and active usage separately, investigate upward memory trends, and set a resource budget before adding features. For large-file workflows, measure parsing and processing as well as disk and network I/O; provide progress feedback when operations exceed one second. section 3.2.4 section 6.1

Table 3.5 Desktop performance metrics
Metric
Measures
Example
Launch time
Time from click to first interactive screen
Application opens and shows content within 3s
Input latency
Delay between user action and visual feedback
Keystroke reflected on screen within 50ms
Resource consumption
CPU and memory usage during idle and active use
App uses under 1% CPU when idle
File operation time
Time to open, save, or sync files
50MB file opens within 3s

Use the desktop metrics table to compare resource consumption with launch time, input latency, and file-operation time. section 3.2.4

How Fast by Default covers it

How deep it goes
Explains desktop targets, idle-versus-active measurement, memory trends, and budget practice without prescribing implementation internals.
Examples
Uses desktop applications, multitasking interference, long-running memory growth, and large-file loading, saving, and synchronization.
What it assumes
Assumes familiarity with software performance measurement while defining user-centered goals, baselines, thresholds, and resource categories.
What you can do after
Diagnose with resource measurements, establish budgets, investigate memory growth, and evaluate trade-offs against responsiveness and user outcomes.
How it connects
Connects resource utilization with performance goals, performance budgets, input latency, memory leaks, file operations, and user satisfaction.

Also explained in

Compare how 13 books explain resource utilization →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.