New blog post

A closer look at New blog post

What this post is about

This is a blog post by the author who previously wrote an introduction to fibers. It describes the design decisions behind a fiber-based job system the author developed for an offline renderer and its asset build pipeline, and explains why fibers were chosen as the foundation for cooperative multithreading.

What you can learn and do from the article

Read about differences between fiber-based job systems and traditional OS-thread job systems: cooperative multitasking, application-controlled scheduling, lower-cost suspension/resumption, and explicit control over stack allocation where supported. The post also covers practical trade-offs such as limited debugger support, subtle low-level bugs, the need for custom synchronization primitives, blocking-call pitfalls, limits around thread-local storage, portability concerns across ABIs, and potential memory-leak issues. The author recommends reading their earlier post for a fiber basics introduction.

Who will find this useful

Engine programmers, renderer developers, or anyone evaluating job system designs who already understands low-level concurrency concepts will get the most from this article. It is aimed at readers comfortable with implementation details and willing to handle extra complexity (custom synchronization, ABI-specific fiber code) to gain finer scheduling control.

Questions people ask about New blog post

Do I need to read anything else first?

Yes - the author recommends reading their previous blog post that introduces fiber basics before this article, because some parts may be hard to follow without that background.

Does the post describe Naughty Dog’s job system?

No - the author explicitly states this article does not describe Naughty Dog’s job system and focuses only on the job system they developed for their offline renderer.

Are fibers always better than threads?

No - the post lists benefits of fibers but also several costs and limitations, and notes fiber-based systems will not benefit every kind of software. The trade-offs determine whether the effort is justified.

New blog post was shared on NexURLs by Nexis on October 31, 2026, in Design & Art.