How Netflix Really Uses Java

Re:How Netflix Really Uses Java by blackoil on Tuesday October 10, 2023 @04:54AM (#37829851)

I think this is a 20% improved utilization of CPU, earlier app was memory-bound or/and GC was consuming CPU. Now app has 20% more CPU available. It should be doing correspondingly more work. This could definitely be written clearly.

[ Parent | on HN ]

Re:How Netflix Really Uses Java by moffkalast on Tuesday October 10, 2023 @05:13AM (#37829967)

> Bakker provided a retrospective of their JDK 17 upgrade that provided performance benefits, especially since they were running JDK 8 as recently as this year. Netflix observed a 20% increase of CPU usage

Seems like it's exactly that, OP cropped out the relevant bit where they list it having an overall performance benefit for that extra CPU time. Otherwise it could be assumed that it just hogs more CPU to get the same result.

[ Parent | on HN ]

Re:How Netflix Really Uses Java by bunderbunder on Tuesday October 10, 2023 @09:31AM (#37831859)

I haven't dealt with this side of Java in a while, but it reflects my experience poking at Java 8 performance. At some (surprisingly early) point you'd hit a performance wall due to saturating the memory bus.

A new GC could alleviate this by either going easier on the memory itself, or by doing allocations in a way that achieves better locality of reference.

[ Parent | on HN ]