The functional guide to listener management (#875)

21. marec 2026 ob 06:39:40 Carol Williams

Concurrency Patterns in PHP

PHP's traditional request-per-process model is simple but limiting. Modern PHP offers several concurrency approaches.

Fork-Based Parallelism

Using pcntl_fork(), a parent process creates child processes that inherit its full state via OS copy-on-write:

$futures = [];
foreach ($chunks as $chunk) {
    $futures[] = run(function () use ($chunk) {
        return processChunk($chunk);
    });
}

$results = array_map(fn ($f) => $f->value(), $futures);

Advantages: Full state inheritance, true parallelism, no serialization overhead for captured variables.

Challenges: Connection management (database, Redis, HTTP clients must be reset in child processes), memory overhead per process.

Async I/O

For I/O-bound workloads, async libraries like ReactPHP or AMPHP multiplex operations on a single thread:

$promises = [];
foreach ($urls as $url) {
    $promises[] = $httpClient->request('GET', $url);
}
$responses = await(all($promises));

Advantages: Low memory footprint, excellent for HTTP calls and database queries.

Challenges: Callback complexity, limited CPU parallelism, ecosystem compatibility.

Choosing the Right Model

| Workload | Best Approach | |----------|--------------| | CPU-bound computation | Fork (pcntl) | | Many HTTP API calls | Async I/O | | Mixed CPU + I/O | Fork with async per child | | Real-time streaming | Event loop (ReactPHP) |

architecture beginner ipsum voluptate

Prijava za objavo komentarja

2 komentarja

Frank Miller komentirano dne 21. mar. 2026, 21:22

Urna nisl sollicitudin id varius orci quam id turpis. Eros diam egestas libero eu vulputate risus. Morbi tempus commodo mattis. In hac habitasse platea dictumst. Potus sensim ad ferox abnoba. Teres talis saepe tractare de camerarius flavum sensorem. Lorem ipsum dolor sit amet consectetur adipiscing elit.

Jane Doe komentirano dne 21. mar. 2026, 21:21

Eros diam egestas libero eu vulputate risus. Curabitur aliquam euismod dolor non ornare. Potus sensim ad ferox abnoba. Ut eleifend mauris et risus ultrices egestas.

To je demo aplikacija zgrajena z ogrodjem Symfony za prikaz priporočenega načina razvoja aplikacij Symfony.

Za več informacij poglejte dokumentacijo Symfony.

Kliknite na ta gumb za prikaz izvorne kode krmilnika in predloge uporabljene za izpis te strani.

src/Controller/BlogController.php at line 272

/**
 * NOTE: when the controller argument is a Doctrine entity, Symfony makes an
 * automatic database query to fetch it based on the value of the route parameters.
 * The '{slug:post}' configuration tells Symfony to use the 'slug' route
 * parameter in the database query that fetches the entity of the $post argument.
 * This is mostly useful when the route has multiple parameters and the controller
 * also has multiple arguments.
 * See https://symfony.com/doc/current/doctrine.html#automatically-fetching-objects-entityvalueresolver.
 */
#[Route('/posts/{slug:post}', name: 'blog_post', requirements: ['slug' => Requirement::ASCII_SLUG], methods: ['GET'])]
public function postShow(Post $post): Response
{
    // Symfony's 'dump()' function is an improved version of PHP's 'var_dump()' but
    // it's not available in the 'prod' environment to prevent leaking sensitive information.
    // It can be used both in PHP files and Twig templates, but it requires to
    // have enabled the DebugBundle. Uncomment the following line to see it in action:
    //
    // dump($post, $this->getUser(), new \DateTime());
    //
    // The result will be displayed either in the Symfony Profiler or in the stream output.
    // See https://symfony.com/doc/current/profiler.html
    // See https://symfony.com/doc/current/templates.html#the-dump-twig-utilities
    //
    // You can also leverage Symfony's 'dd()' function that dumps and
    // stops the execution

    return $this->render('blog/post_show.html.twig', ['post' => $post]);
}

templates/blog/post_show.html.twig at line 1

RSS objav bloga