Why design patterns matter in PHP - Performance Analysis

Time Complexity: Why design patterns matter

O(n)

Understanding Time Complexity

When we use design patterns in PHP, it helps us organize code better. But how does this affect how fast our program runs?

We want to see how the time it takes to run changes when we use these patterns.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

class Logger {
    public function log($message) {
        echo $message . "\n";
    }
}

class User {
    private Logger $logger;
    public function __construct(Logger $logger) {
        $this->logger = $logger;
    }
    public function login(array $users) {
        foreach ($users as $user) {
            $this->logger->log("User " . $user . " logged in.");
        }
    }
}

$logger = new Logger();
$user = new User($logger);
$user->login(['Alice', 'Bob', 'Charlie']);
    

This code uses a simple Logger design pattern to separate logging from user actions. It logs each user login.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through the list of users to log each login.
• How many times: Once for each user in the input array.

How Execution Grows With Input

As the number of users grows, the logging happens more times, one for each user.

Input Size (n)	Approx. Operations
10	10 logging calls
100	100 logging calls
1000	1000 logging calls

Pattern observation: The work grows directly with the number of users. More users mean more logs.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line with the number of users.

Common Mistake

[X] Wrong: "Using design patterns always makes the code slower because of extra classes."

[OK] Correct: Design patterns organize code but usually do not add loops or heavy work. The main time depends on how many times you do important tasks, like logging each user.

Interview Connect

Understanding how design patterns affect time helps you explain your code choices clearly. It shows you think about both good design and performance.

Self-Check

"What if the logger also wrote to a file inside the loop? How would the time complexity change?"