liveBook · Manning

Parallelism

As explained in Learn Docker in a Month of Lunches, Second Edition

Parallelism is the concurrent execution of multiple computational operations or data transfers.

Parallelism executes multiple transfers concurrently. Docker Engine downloads image layers at the same time—three by default—so splitting large data across layers can improve pull performance. section 17.4

Apply parallel layer transfers when optimizing large Docker images:

  • Prefer multiple layers for large transfer-heavy images, while recognizing that explicitly listing every file is more brittle. section 17.4

ML dataset image

A one-layer target copies days 70–79 with a wildcard; a multi-layer target copies each data file separately. Pulling the multi-layer image can be substantially faster on a new machine.

How Learn Docker in a Month of Lunches, Second Edition covers it

How deep it goes
Explains concurrent layer downloads, configurable concurrency, Dockerfile alternatives, and transfer trade-offs.
Examples
Compares ML dataset images that copy days 70–79 into one layer or separate layers.
What it assumes
Assumes familiarity with Docker images, Dockerfiles, build targets, and image layers.
What you can do after
Evaluate Docker image transfer performance by building alternative targets and comparing sizes and layer histories.
How it connects
Connects Docker layers, image pulls, Dockerfile optimization, image history, and autoscaling container platforms.

Also explained in

Compare how 38 books explain parallelism →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.