A way to stop GC wasting CPU time on long-lived objects (GC generations or something else)

Description

PHP's GC is currently unsuited to long-running applications because of the lack of GC generations.

Any application which has long-lived objects with many descendents (such as PocketMine-MP's Server) will currently experience significant performance hits from GC runs due to the expense of repeatedly scanning complex dependencies of these objects.

I haven't dived deep into this problem, but I did verify that just the Server alone winding up in the GC root buffer in PocketMine-MP (which it should never do, being an object that stays alive for almost the entire process) costs 1.7 ms of GC time on a 12700k. An average GC run in PM during normal operation costs somewhere in the ballpark of 15ms, despite creating almost zero cycles.

This is a massive performance impact to PM on account of its update cycle taking place every 50 ms, so a 15ms GC pause is serious business.

Runtimes like .NET and Java have GC generations to avoid this problem, which avoid frequently scanning complex long-lived objects.

I understand that the benefit to PHP is relatively small, given that the primary use case is to serve short-lived web requests, but implementing generations in GC would positively affect performance of long-lived applications.

Inizia con l’esempio collegato di PocketMine-MP src/Server.php per comprendere il grafo di oggetti longevi e il costo di GC segnalato. Individua quindi l’implementazione del GC di PHP e i test pertinenti, riproduci la scansione ripetuta descritta qui e considera completato un approccio testato che riduca il lavoro per gli oggetti longevi preservando al contempo la raccolta dei cicli.