Fibers for concurrency in PHP - Time & Space Complexity

Time Complexity: Fibers for concurrency

O(n * m)

Understanding Time Complexity

When using fibers for concurrency in PHP, it's important to understand how the program's running time changes as tasks increase.

We want to see how the number of tasks affects the total execution time when fibers switch between them.

Scenario Under Consideration

Analyze the time complexity of the following PHP code using fibers.

$fiber1 = new Fiber(function() {
    for ($i = 0; $i < 5; $i++) {
        echo "Fiber 1: $i\n";
        Fiber::suspend();
    }
});

$fiber2 = new Fiber(function() {
    for ($i = 0; $i < 5; $i++) {
        echo "Fiber 2: $i\n";
        Fiber::suspend();
    }
});

$fiber1->start();
$fiber2->start();

while (!$fiber1->isTerminated() || !$fiber2->isTerminated()) {
    if (!$fiber1->isTerminated()) $fiber1->resume();
    if (!$fiber2->isTerminated()) $fiber2->resume();
}
    

This code runs two fibers that each print numbers 0 to 4, switching between them after each print.

Identify Repeating Operations

Look at what repeats in this code:

• Primary operation: Each fiber runs a loop 5 times, printing and suspending.
• How many times: Each fiber resumes 5 times, so total 10 resumes combined.

How Execution Grows With Input

Imagine increasing the number of fibers or loop counts:

Input Size (n)	Approx. Operations
10 (fibers or loop count)	About 10 x 5 = 50 resumes
100	About 100 x 5 = 500 resumes
1000	About 1000 x 5 = 5000 resumes

Pattern observation: The total steps grow roughly linearly with the input if only one of fibers or loop counts increases.

Final Time Complexity

Time Complexity: O(n * m)

This means the total work grows by multiplying the number of fibers (n) and the number of steps each fiber runs (m).

Common Mistake

[X] Wrong: "Fibers run all tasks at the same time, so time stays the same no matter how many tasks there are."

[OK] Correct: Fibers switch tasks but still run each step one after another, so total time adds up with more tasks.

Interview Connect

Understanding how fibers affect time helps you explain concurrency clearly and shows you know how programs handle multiple tasks efficiently.

Self-Check

"What if we changed the code to run fibers in parallel without suspending? How would the time complexity change?"

Practice

1. What is the main purpose of using Fiber in PHP?

easy

A. To speed up database queries automatically

B. To create permanent background threads

C. To pause and resume code execution for concurrency

D. To replace all loops with asynchronous calls

Solution

1. Step 1: Understand Fiber's role

   Fibers allow pausing and resuming code blocks, enabling concurrency without threads.

2. Step 2: Compare options

   Only To pause and resume code execution for concurrency correctly describes Fibers' purpose; others describe unrelated features.

3. Final Answer:

   To pause and resume code execution for concurrency -> Option C

4. Quick Check:

   Fibers = pause and resume concurrency [OK]

Hint: Fibers let you pause and resume code easily [OK]

Common Mistakes:

• Thinking Fibers create real threads
• Assuming Fibers speed up database automatically
• Confusing Fibers with async loops

2. Which of the following is the correct way to start a Fiber in PHP?

easy

A. $fiber->run();

B. $fiber->execute();

C. $fiber->begin();

D. $fiber->start();

Solution

1. Step 1: Recall Fiber methods

   The Fiber class uses start() to begin execution.

2. Step 2: Check other options

   Methods like run(), begin(), and execute() do not exist for Fiber.

3. Final Answer:

   $fiber->start(); -> Option D

4. Quick Check:

   Fiber starts with start() method [OK]

Hint: Use start() to begin Fiber execution [OK]

Common Mistakes:

• Using run() instead of start()
• Trying to call execute() or begin()
• Confusing Fiber methods with thread methods

3. What will be the output of this PHP code using Fiber?

$fiber = new Fiber(function(): void {
    $value = Fiber::suspend('paused');
    echo "Resumed with: $value";
});

echo $fiber->start();
$fiber->resume('data');

medium

A. pausedResumed with: data

B. Resumed with: datapaused

C. paused

D. Resumed with: data

Solution

1. Step 1: Analyze Fiber start()

   The start() runs until Fiber::suspend('paused'), which returns 'paused'. So, echo outputs 'paused'.

2. Step 2: Analyze Fiber resume()

   The resume('data') continues after suspend, echoing "Resumed with: data".

3. Final Answer:

   pausedResumed with: data -> Option A

4. Quick Check:

   start() returns suspend value, resume() continues [OK]

Hint: start() returns suspend value, resume() continues execution [OK]

Common Mistakes:

• Assuming start() returns void
• Thinking resume() returns suspend value
• Mixing order of output strings

4. Identify the error in this Fiber code snippet:

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

$fiber->resume();

medium

A. Fiber::suspend() cannot be called without a value

B. Fiber must be started with start(), not resume() first

C. Fiber constructor requires a return type declaration

D. Fiber cannot echo strings inside its function

Solution

1. Step 1: Check Fiber start method usage

   Fibers must be started with start() before calling resume().

2. Step 2: Validate other options

   Calling Fiber::suspend() without value is allowed; no return type needed; echo is valid inside Fiber.

3. Final Answer:

   Fiber must be started with start(), not resume() first -> Option B

4. Quick Check:

   start() first, then resume() [OK]

Hint: Always start Fiber with start() before resume() [OK]

Common Mistakes:

• Calling resume() before start()
• Thinking suspend() needs a value
• Expecting Fiber function to require return type

5. You want to run two Fibers concurrently to simulate two tasks. Which approach correctly switches between them to print alternating messages?

$fiber1 = new Fiber(function() {
    for ($i = 0; $i < 3; $i++) {
        echo "A$i ";
        Fiber::suspend();
    }
});

$fiber2 = new Fiber(function() {
    for ($i = 0; $i < 3; $i++) {
        echo "B$i ";
        Fiber::suspend();
    }
});

// Which code below correctly alternates execution?

A) {
    $fiber1->start();
    $fiber2->start();
    $fiber1->resume();
    $fiber2->resume();
}

B) {
    $fiber1->start();
    $fiber1->resume();
    $fiber2->start();
    $fiber2->resume();
}

C) {
    $fiber1->start();
    $fiber2->start();
    $fiber2->resume();
    $fiber1->resume();
}

D) {
    $fiber1->start();
    $fiber2->start();
    $fiber1->resume();
    $fiber1->resume();
}

hard

A. Start both fibers, then alternate resume calls: fiber1->resume(), fiber2->resume()

B. Start and resume fiber1 twice before starting fiber2

C. Start both fibers, then resume fiber2 before fiber1

D. Start both fibers, then resume fiber1 twice without resuming fiber2

Solution

1. Step 1: Understand Fiber suspension

   Each Fiber suspends after printing one message, so to alternate, we must resume them in turn.

2. Step 2: Analyze options for alternating resumes

   Start both fibers, then alternate resume calls: fiber1->resume(), fiber2->resume() starts both fibers, then resumes fiber1 and fiber2 alternately, producing alternating output. Others resume one fiber multiple times or in wrong order.

3. Final Answer:

   Start both fibers, then alternate resume calls: fiber1->resume(), fiber2->resume() -> Option A

4. Quick Check:

   Alternate resume calls for concurrency [OK]

Hint: Alternate resume calls to switch between fibers [OK]

Common Mistakes:

• Resuming one fiber multiple times before the other
• Starting fibers but not resuming correctly
• Resuming fibers in wrong order