Just confirmed that the binary in the Docker image (bookworm) has much lower performance than Github Releases

[bohanwood]

• Docker image
• GitHub Release

Machine:

• i5-12500H (16C)
• 16G RAM
• WSL2

It's a Symfony project, using the symfony-docker template.

The interesting thing:
When using MySQL there's not much difference but when using SQLite as DB,
dunglas/frankenphp can only have 2000-3000 QPS while the GitHub one can go 5000-7000 QPS

Sorry for can't provide reproducible environment for now

[dunglas]

Have you checked that the file containing the SQLite DB isn't in a volume or something like that?

[withinboredom]

I do believe you want the sqlite db running in a volume, otherwise it is going to be participating in the COW filesystem, which is likely quite slow.

[bohanwood]

I did this in a docker compose. Both container uses the DB in a named volume.

[bohanwood]

The biggest difference is that they use different PHP:

1. Container A: FROM php:8.3 and downloaded the static frankenphp binary
2. Container B: FROM dunglas/frankenphp:1-php8.3

Same SQLite DB in same named volume. A has better QPS than B.

When checking phpinfo,

• A did not load php.ini from /usr/local/etc/php. And the PDO SQLite version is 3.43.2.
• B loaded php.ini from /usr/local/etc/php and extensions from install-php-extensions in the Dockerfile. And the version is 3.40.1.

So basically they use completely different PHP environment. However this still didn't show what leds to the performance difference.

Any ideas?

[withinboredom]

Musl vs. libc vs. static compilation vs. shared dependencies? It could also be that the host system was under different priorities and loads at the time you tested ... or even the order can affect it (cold vs. hot kernel file caches). There can also be differences in workloads (for example, I see the exact opposite of what you see on my test workloads).

There are simply too many variables for there to be a definitive "this is better than that."