php / php/php-src

PHP-8.5.0: performance discrepancy in container cold-start

Ouverte
#20,576 10 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Bug Status: Needs Triage
Langage dominant
C
Étoiles
40.4k
Forks
8.2k
Merge moyen
2 j 13 h
PR mergées (30 j)
96

Description

Description

I am currently evaluating the performance of a stock Laravel application within a containerized environment and have observed a noticeable performance difference between PHP 8.4 and PHP 8.5.

Observation
Image

In a direct comparison of cold startup times, the container running on php:8.4-fpm is consistently faster than the one on php:8.5-fpm. My initial benchmarks show the PHP 8.4 container starting up around 300ms faster than the PHP 8.5 container. This is contrary to my expectation that a newer version would yield similar or improved performance.

Request for Input

I would like to understand what might be contributing to this performance gap. Could you provide any insights on the following:

  • Default Configuration Changes: Are there any significant changes to the default php.ini or PHP-FPM configuration values between versions 8.4 and 8.5 that could impact startup performance?
  • Container Image Differences: Are there any known differences in the official php-fpm Docker images for these versions that might explain the slower startup time for PHP 8.5?
  • Known Performance Regressions: Are there any acknowledged performance regressions in PHP 8.5, particularly concerning startup, that the community is aware of? While benchmarks often show similar or slightly improved performance for newer PHP versions, my findings suggest a potential issue in this specific context.

My goal is to ensure we are using the most performant and up-to-date version of PHP. Any guidance or suggestions on where to investigate further would be greatly appreciated.

Thank you for your time and assistance.

Dockerfiles are different just the 8.4 vs 8.5 version

#FROM php:8.5-fpm
FROM php:8.5-fpm AS builder

# Get latest Composer
COPY --from=composer:latest /usr/bin/composer /usr/bin/composer

# Install system dependencies required by Composer
RUN apt-get update && apt-get install -y git zip unzip libzip-dev && docker-php-ext-install zip

# Set working directory
WORKDIR /var/www/html

# Copy rest of the application source code
COPY . .

# Install Composer dependencies
RUN composer install --no-dev --optimize-autoloader

# ---- Runtime Stage ----
FROM php:8.5-fpm

# Set working directory
WORKDIR /var/www/html

# Copy application files from the builder stage
COPY --from=builder /var/www/html .

# Expose port 8080 and start php-fpm server
EXPOSE 8080
CMD php artisan serve --host=0.0.0.0 --port=8080

The test was made with exact same codebase, exact same requests, in exact same time, region etc.. 100% cold starts, measured in Google Cloud Run platform, using the same official container slow start latency metrics. Results are consistent.

PHP Version
PHP 8.5.0
Operating System

No response

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par comparer les Dockerfiles php:8.4-fpm et php:8.5-fpm présentés ainsi que les configurations officielles des images, puis reproduisez le benchmark de démarrage à froid dans Google Cloud Run avec l’application Laravel. Vérifiez les différences entre PHP-FPM et la configuration PHP par défaut, et comparez les résultats avec des requêtes identiques. La tâche est terminée lorsqu’une différence de configuration ou d’image est identifiée, ou lorsqu’une régression reproductible du démarrage de PHP 8.5 est confirmée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
docker, google-cloud, laravel, php
Domaine
backend, cloud, performance
Type d'issue
Bug
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
À clarifier
Accessibilité débutants
35/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.