You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If using glibc is a big undertaking maybe some of the mitigations suggested by FrankenPHP can be implemented like using mimalloc
I just want to know what are your thoughts. It would be a better situation if FrankenPHP claims were also backed by some detailed performance report so we would be aware of what percentages are we talking about.
The text was updated successfully, but these errors were encountered:
Hello @csandanov
Thank you for taking the time to read this and to maintain such a great set of docker images.
I understand that frankenphp might be interesting but my point was not about it.
I always considered the wodby images more production-ready and I wanted to scratch a little bit on the reason why Alpine (and musl by extension) was chosen for these docker images when debian (with glibc) is the default of the official PHP images.
I stumbled upon this piece of docs for FrankenPHP claiming that musl is not appropriate for production environments due to performance
https://frankenphp.dev/docs/performance/#dont-use-musl
Is there any plans to have a glibc variant?
The only issue I found is the from 7 years ago
#4
If using glibc is a big undertaking maybe some of the mitigations suggested by FrankenPHP can be implemented like using mimalloc
I just want to know what are your thoughts. It would be a better situation if FrankenPHP claims were also backed by some detailed performance report so we would be aware of what percentages are we talking about.
The text was updated successfully, but these errors were encountered: