# Language & runtime

> What does a version, compiler or runtime setting actually change?

- Status: Open
- Record count: 3
- Source: https://www.muhammetsafak.com.tr/en/research/program/dil-runtime/
- Language: en-US
- Author: Muhammet Şafak

---
What version upgrades, compiler and runtime settings change on the same workload: JIT, opcache, GC and memory behaviour.

## Findings ledger

### Laravel's preload curve: 123 files buy eight times what the last 1,912 do

- Question: How far can a curated preload take Laravel, and what does each slice cost in start-up time?
- Finding: The curve is not proportional to volume. The first 1,592 files — Laravel's own framework — buy 30 ms and add 1.2 seconds to start-up. The next 1,094 Symfony files buy 9.5 ms for free. The **123 files** after that (psr, carbon) buy 15.7 ms, more than the 1,094 before them. And the last 1,912 buy 1.8 ms while adding another 1.2 seconds. So the blanket preload the earlier record measured as a ceiling is the worst point on the curve that is not the origin: stopping at 2,809 files gives 12.77 ms for 1,514 ms of start-up, while 4,721 files ask 2,691 ms to reach 10.96 ms.
- https://www.muhammetsafak.com.tr/en/research/laravel-preload-curve/
- Markdown: https://www.muhammetsafak.com.tr/en/research/laravel-preload-curve.md

### opcache preload cuts the deploy bill by up to fourteen times — but five of seven frameworks do not hand it to you

- Question: With `opcache.preload` on, how long is the first request seven PHP frameworks serve after a deploy, what does the gain cost, and who can actually have it?
- Finding: Preload shortens the cold first request by between 3.5× and 14.2×: Symfony drops from 35.58 ms to 2.50 ms, down to Phalcon's bare figure. But only two of the seven candidates — Symfony and CodeIgniter — publish a preload file of their own; for the other five the gain sits on the table waiting for the user to write one. Writing one is not as easy as it looks: a preload generated blindly from the classmap never brings Symfony up at all, and on CodeIgniter it does worse (5.29 ms) than the hand-picked official file (3.13 ms). And the cost does not vanish: Laravel's classmap preload takes the 62 ms it saves each visitor and writes it back as 2,340 ms of php-fpm start-up.
- https://www.muhammetsafak.com.tr/en/research/opcache-preload-deploy-bill/
- Markdown: https://www.muhammetsafak.com.tr/en/research/opcache-preload-deploy-bill.md

### The PHP ecosystem does not wait for a new release — but it does not declare support either

- Question: After a PHP release ships, when do the 500 most-installed Composer packages declare that they support it, and how much does that declaration actually say?
- Finding: 43.5% of installs arrive on a constraint with no upper bound at all — `symfony/console` says `>=8.4.1` today, which claims support for PHP 12 as well. Of the 280 packages that do close the top, 247 made the commitment before the version existed: `guzzlehttp/guzzle` covered 8.4 in October 2020, four years early. That leaves 33 packages that genuinely waited, at a median of 325 days. The raw medians fall version over version and read as an ecosystem speeding up; restricted to an equal observation window the trend reverses (238 → 215 → 325 days).
- https://www.muhammetsafak.com.tr/en/research/php-version-support-declarations/
- Markdown: https://www.muhammetsafak.com.tr/en/research/php-version-support-declarations.md