Understanding PHP 8.1 Fibers: How They Work and Their Limitations

PHP 8.1 introduced Fibers, a cooperative multitasking feature that lets developers pause and resume specific parts of code without blocking the entire PHP process. While Fibers do not enable true asynchronous execution, they provide powerful task‑management capabilities.

What Are PHP Fibers?

Fibers are a cooperative multitasking mechanism allowing code sections to be suspended and later resumed, effectively acting like special functions that hand control back to the main script.

Key Characteristics of Fibers:

Can be started, paused, and resumed.

Run within a single PHP process without involving multiple threads.

Especially suitable for building non‑blocking code.

What Happens When a Fiber Is Suspended?

Calling Fiber::suspend() returns control to the main script, allowing the main program to continue while the fiber remains paused until resume() is invoked.

$fiber = new Fiber(function () {
    echo "Fiber started\n";
    Fiber::suspend();
    echo "Fiber resumed\n";
});

echo "Before Fiber\n";
$fiber->start();
echo "After Fiber Start\n";
$fiber->resume();
echo "After Fiber Resume\n";

Output:

Before Fiber
Fiber started
After Fiber Start
Fiber resumed
After Fiber Resume

Does Resuming a Fiber Block the Main Process?

Calling Fiber::resume() temporarily blocks the main process until the fiber finishes or suspends again, because PHP remains single‑threaded.

$fiber = new Fiber(function () {
    echo "Processing Fiber...\n";
    sleep(2); // Simulates a blocking task
    echo "Fiber Done\n";
});

echo "Before Fiber\n";
$fiber->start();
echo "Between Fiber Start and Resume\n";
$fiber->resume();
echo "After Fiber\n";

Output:

Before Fiber
Processing Fiber...
Fiber Done
Between Fiber Start and Resume
After Fiber

During the sleep(2) call, the fiber blocks the main process, illustrating that Fibers do not magically achieve parallelism.

How Fibers Remain "Non‑Blocking"

Fibers are non‑blocking in the sense that they can hand control back to the main script or an event loop, allowing other tasks to run while a fiber is paused.

Long‑running or waiting tasks (e.g., database queries, API calls) can be paused.

Other tasks can proceed concurrently.

When the paused task is ready, the fiber is resumed.

This enables simulation of asynchronous behavior in a single‑threaded environment.

Fibers and Event Loops

Fibers are typically combined with an event loop (e.g., ReactPHP or Amp) to achieve true non‑blocking operations. The event loop tracks multiple tasks, pauses a fiber when it encounters a blocking operation, processes other tasks, and resumes the fiber once the operation completes.

Why Fibers Are Not Truly Asynchronous

Unlike JavaScript or Node.js, PHP fibers execute synchronously within a single process; they merely allow developers to manually control when a task pauses and resumes, providing cooperative multitasking without parallel execution.

Fibers do not introduce parallelism; tasks run sequentially.

They are a tool for more efficient task management and for writing non‑blocking code in a linear style.

Benefits of using Fibers include improved task management, the ability to build non‑blocking workflows when paired with an event loop, and simpler synchronous execution when resumed, avoiding complex callbacks or promises.

For truly parallel processing, external solutions such as extensions or separate processes are still required.