Responsiveness

As explained in Elixir in Action, Third Edition

Responsiveness is the ability of a system to handle requests within an acceptably short time under normal or adverse conditions.

Responsiveness is a system’s ability to handle requests within an acceptably short time, even as load rises or unexpected errors occur. It is a system-level property alongside scalability, fault tolerance, and high availability. section 1.1 section 1.1.1

BEAM systems protect responsiveness through several implementation choices:

• Preemptive schedulers give each process a small execution window, preventing one long-running process from blocking the system. section 1.1.2
• Separate I/O threads or kernel polling prevent processes waiting on I/O from stopping other processes. section 1.1.2
• Per-process garbage collection avoids system-wide pauses and can run concurrently with ordinary processing on other cores. section 1.1.2
• Concurrency lets the system serve multiple requests concurrently and degrade more gracefully under overload. section 12.2.6

A highly concurrent service

A distributed to-do system uses BEAM processes to handle requests concurrently. Frequent preemption keeps lengthy tasks from blocking the whole service, while isolated garbage collection supports fairly constant latency. Adding machines or nodes provides further capacity as demand grows. section 12.2.6

Figure 1.1 Concurrency in the Erlang virtual machine

Use the virtual-machine diagram to visualize how schedulers interleave Erlang processes. section 1.1.2

How Elixir in Action, Third Edition covers it

How deep it goes

Explains scheduler preemption, I/O handling, and per-process garbage collection, stopping short of detailed runtime implementation.

Examples

Uses a distributed to-do system, preemptive scheduling, concurrent garbage collection, and a BEAM concurrency diagram.

What it assumes

Assumes familiarity with system availability and load while introducing BEAM processes and scheduling as responsiveness mechanisms.

What you can do after

Evaluate how BEAM concurrency mechanisms preserve latency when tasks run long, I/O waits, garbage collection occurs, or load increases.

How it connects

Connects responsiveness with concurrency, scalability, fault tolerance, distribution, and high availability.

liveBookmanning.com

Read Elixir in Action, Third Edition on liveBook Get the book at manning.com

Related concepts

• autonomycontrasts with · Autonomy is the capacity or degree to make decisions and act independently within a defined responsibility or set of limits.
• thresholdconfigured by · A threshold is a boundary value against which a quantity is compared to determine whether a condition is met or an action or decision is triggered.
• concurrencyproduced by · Concurrency is the structuring or execution of multiple computational activities so their progress overlaps in time, whether or not they run simultaneously.
• scalabilityused by · Scalability is the ability of a system, process, or method to accommodate increasing workload, size, or demand while maintaining acceptable operation.
• reliabilityused by · Reliability is the ability of a system or process to perform its intended functions consistently and dependably under specified conditions and over time.
• meancontrasts with · A mean is a measure of central tendency, calculated as the arithmetic average of values or, for a random variable, as the probability-weighted average of its possible values.

This explainer was generated by Manning's knowledge graph from the text of Elixir in Action, Third Edition. The section links point to the parts of the book it draws on.