[RFC] True native async implementations

Highlights

🏅 Top 1 performance in synthetic benchmark
⚡ 30,000% faster latency in Laravel

RFC: https://wiki.php.net/rfc/true_async
Source: https://github.com/true-async/php-src/tree/true-async-stable

True Async Author: @EdmondDantes

Interests

There is also quite a bit of interest in true async as the exchanges here https://externals.io/message/129690#129944 and here https://github.com/orgs/true-async/discussions/9

Description

It was demonstrated that PHP-based framework can beat many frameworks with async, see here:

https://www.http-arena.com/leaderboard/#v=composite&res=mem

It should be noted in the past, during techempower benchmark, actix is among the top contenders in web performance, but in httparena, php async framework scored higher with async/coroutine. While php is not entirely a framework, native async/coroutine is a promising potential

In other works, it also demonstrated massive performance improvement in average latency in Laravel from 4000 ms to 13ms for the same workload.

Misconceptions

• Myth 1

  Myth: Native async will mess up ALL of existing synchronous PHP code and projects globally!

  Truth: Actually no, you have to explicitly define a function/class/namespace to have an async property, otherwise all synchronous codes and projects will happily run as usual as if there is no native async.

• Myth 2

  Myth: Great, now I have to think async when coding new project

  Truth: Actually no, just DON'T define your functions/class/namespace as async then you will be happy with your old php self

Commencez par le PHP RFC lié et la branche de code source true-async-stable, puis examinez les discussions référencées et le contexte des benchmarks. L’issue ne définit pas de fichiers spécifiques, de tests, de limites d’implémentation ni de critères d’acceptation ; sa réalisation nécessiterait donc d’abord de convenir d’une conception et d’un périmètre.