phpPHP Community
Community homeNews Release notes PHP wiki Web directory Multi-levelFeatured packages Best practices Q&A Jobs 38

PHP Community · Choosing PHP: I turned 5 options into a side-by-side comparison

23
phpr/php·posted by dev_zhou·5 minutes agoAnnouncement

Choosing PHP: I turned 5 options into a side-by-side comparison

It took me two weeks of on-and-off digging and plenty of wrong turns. Writing the process down as it happened so the next person spends less time.

One last trap: in container environments remember to adjust the memory-related parameters in step. Otherwise the host limit and the process expectation disagree, and the symptom is intermittent, unreproducible failure.

We also fixed monitoring along the way: replaced average-based alerts with percentiles and split them per endpoint. False alerts dropped by about seventy percent and the on-call rotation visibly cheered up.

Jjvns.caExternal link · opens in a new tab
11 comments

11 comments

M
Sswoole_lee·1 hour ago

I just read the PHP source — the author actually explains the reasoning in a comment, roughly "so that it degrades into predictable behaviour in extreme cases".

480
Hhuang_keOP·12 minutes ago

Thanks for sharing real numbers — far more useful than the articles that only cover concepts.

222
Kkernel_panic·1 hour ago

Sharing our numbers, 8 cores 16GB, same scenario:

| Concurrency | P50 | P99 |
|---|---|---|
| 200 | 12ms | 88ms |
| 500 | 31ms | 340ms |

P99 clearly collapses at 500 concurrency, which lines up with your knee point.

92
Sslow_query·just now

Has anyone run a controlled experiment? I did, reducing it to a single variable, and the difference was 4% — within noise. So I suspect the main cause is something else.

94
Lli_ming·3 minutes ago

We have run this in production for two years without hitting it. That said, we never reached this scale, so our experience is not really evidence here.

5
Aalice_dev·yesterday

Saved. I am reworking this area this week — this saves a lot of wrong turns.

137
Lli_mingMod·5 hours ago

Can you give a minimal reproduction? I ran it locally for ten minutes and could not reproduce on macOS with the latest version.

12
Mmike_xuOP·28 minutes ago

There is actually a simpler fix that needs no architecture change: move this check up to the gateway and the problem disappears. The cost is one extra lookup at the gateway.

69
Llinlin·3 minutes ago

Agreeing with the above. One addition: with this option enabled the GC count in your metrics doubles, so adjust the alert threshold at the same time or it will keep firing.

54
Hhuang_ke·2 hours ago

A question: what changes in a container with a 512Mi memory limit? That is how we run it in production.

229
Rrase·1 hour ago

I see point 3 differently. The trade-off depends on your read/write ratio: read-heavy with little writing means caching actually widens the inconsistency window.

25

This is the post detail page /en/c/php/post/p3. Posts and comments are generated deterministically from a seeded PRNG, so the same post always renders the same content and the link can be shared, reloaded and indexed. In production this page reads MySQL for the post, Redis for hot-post caching, and fetches the whole comment tree in a single query on the path column.

See the database schema →