liveBook · Manning

Parallelism

As explained in High Performance Unity Game Development

Executing computational work concurrently by dividing it into tasks.

Parallelism divides a workload into tasks that can run across multiple CPU cores. Unlike SIMD, which processes multiple values with one operation on a single core, parallelism uses multiple cores to do work simultaneously. section 12.0

In Unity, Jobs can split data across threads. A data-oriented design with flat arrays provides a foundation for adding parallel processing, though the extra tools increase code complexity. section 12.0 section 12.5

Updating enemy positions

Use Jobs with TransformAccessArray to update enemy GameObject positions in parallel. This adds scheduling and completion-wait overhead, so use it when transform updates are a bottleneck. section 12.5

How High Performance Unity Game Development covers it

How deep it goes
Defines task splitting across cores and notes scheduling overhead, without detailing job implementation.
Examples
Illustrates parallel updates of enemy GameObject positions with Jobs and TransformAccessArray.
What it assumes
Builds on data-oriented design and flat arrays as a foundation for adding parallel processing.
What you can do after
Apply it via Unity Jobs and TransformAccessArray to parallelize GameObject transform updates when they are the bottleneck.
How it connects
Connects parallel processing to Jobs, data-oriented design, SIMD, Burst, ECS, and TransformAccessArray.

Also explained in

Compare how 55 books explain parallelism →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of High Performance Unity Game Development. The section links point to the parts of the book it draws on.