[jrpelkonen]

Great write up, focusing on facts without fingerpointing.

But I must admit I was somewhat surprised Cloudflare was not already proactively monitoring and tuning the generation sizes. Configuring the generation sizes was table stakes for JVM performance tuning back in the day.

[ErikCorry]

We choose to be transparent when we fix stuff, even if it makes us look a bit silly :-) . We are certainly installing more logging and tracking of this sort of thing!

In general I think the GC should auto-adapt as much as possible. It's a bit of an admission of defeat for the GC author if the users have to spend a lot of time tuning the parameters. What we are doing here is removing the tuning that was no longer correct, and allowing V8 more latitude to pick its own young gen size.

[noir_lord]

Not silly at all - with such a massive surface even specialists on a part of it don't see all of their part all of the time :).

Any dev who's been around a while has been bitten by many assumptions or straight blindspots many times.

"Huh..that's weird" has been the entry point to some truly astounding ones over the years for me at least.

[jrpelkonen]

I appreciate the candor, and I agree that auto-adaptation probably makes sense in this use case because the workloads are unknown and varied.