php / php/php-src

PHP-8.5.0: performance discrepancy in container cold-start

Offen
#20,576 10 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bug Status: Needs Triage
Vorherrschende Sprache
C
Sterne
40.4k
Forks
8.2k
Ø Merge
2 T. 13 Std.
Gemergte PRs (30 T.)
96

Beschreibung

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

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Rechercherichtung

Beginne mit dem Vergleich der gezeigten php:8.4-fpm- und php:8.5-fpm-Dockerfiles sowie der offiziellen Image-Konfigurationen und reproduziere anschließend den Cold-Start-Benchmark in Google Cloud Run mit der Laravel-Anwendung. Prüfe die Unterschiede zwischen PHP-FPM und der standardmäßigen PHP-Konfiguration und vergleiche die Ergebnisse unter identischen Requests. Als erledigt gilt die Identifizierung eines Konfigurations- oder Image-Unterschieds oder die Bestätigung einer reproduzierbaren Startregression in PHP 8.5.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
docker, google-cloud, laravel, php
Bereich
backend, cloud, performance
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.