How Netflix uses Java

#1

Post by ivanche » Tue, Oct 10, 2023, 7:25 AM UTC

Re: How Netflix uses Java

#2

Post by madaxe_again » Tue, Oct 10, 2023, 8:05 AM UTC

Ah, the way they break out artwork calls explains the weird behaviour I see with my U.K. Netflix account in Portugal - English titles, Portuguese posters, regardless of language preferences.

Re: How Netflix uses Java

#3

Post by jarym » Tue, Oct 10, 2023, 8:11 AM UTC

Interesting the article jumps straight from REST to GraphQL and forgets Falcor[0] - Netflix's alternative vision for federated services. For a while it looked like it might be a contender to GraphQL but it never really seemed to take off despite being simpler to adopt.

[0] https://netflix.github.io/falcor/

Re: How Netflix uses Java

#4

Post by ValtteriL » Tue, Oct 10, 2023, 8:31 AM UTC

>Netflix observed a 20% increase of CPU usage on JDK 17 compared to JDK 8. This was mostly due to the improvements in the G1 garbage collector.

Help me here, why do GC improvements cause CPU increase?

Re: How Netflix uses Java

#5

Post by radomir_cernoch » Tue, Oct 10, 2023, 8:35 AM UTC

ValtteriL wrote: post #4

>Netflix observed a 20% increase of CPU usage on JDK 17 compared to JDK 8. This was mostly due to the improvements in the G1 garbage collector. Help me here, why do GC improvements cause CPU increase?

Also interested! We saw basically the exact opposite. :-)

Re: How Netflix uses Java

#6

Post by tpm » Tue, Oct 10, 2023, 8:39 AM UTC

ValtteriL wrote: post #4

>Netflix observed a 20% increase of CPU usage on JDK 17 compared to JDK 8. This was mostly due to the improvements in the G1 garbage collector. Help me here, why do GC improvements cause CPU increase?

I read it as a good thing: GC improvements -> more available memory -> more work done by the CPU. But still would be interested in more detail.

Re: How Netflix uses Java

#7

Post by pyeri » Tue, Oct 10, 2023, 8:40 AM UTC

ValtteriL wrote: post #4

>Netflix observed a 20% increase of CPU usage on JDK 17 compared to JDK 8. This was mostly due to the improvements in the G1 garbage collector. Help me here, why do GC improvements cause CPU increase?

It's like hiring more workers to accomplish the exact same output as before. "See, I achieved 20% growth in my targets!", some recruiter will say!

Re: How Netflix uses Java

#8

Post by dewey » Tue, Oct 10, 2023, 8:53 AM UTC

In case you are wondering what LOLOMO stands for, it's "List of List of Movies".

Re: How Netflix uses Java

#9

Post by blackoil » Tue, Oct 10, 2023, 8:54 AM UTC

ValtteriL wrote: post #4

>Netflix observed a 20% increase of CPU usage on JDK 17 compared to JDK 8. This was mostly due to the improvements in the G1 garbage collector. Help me here, why do GC improvements cause CPU increase?

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.

Re: How Netflix uses Java

#10

Post by matsemann » Tue, Oct 10, 2023, 8:54 AM UTC

ValtteriL wrote: post #4

>Netflix observed a 20% increase of CPU usage on JDK 17 compared to JDK 8. This was mostly due to the improvements in the G1 garbage collector. Help me here, why do GC improvements cause CPU increase?

The CPU can do more tasks without being limited by memory pressure, perhaps?

I guess it depends on if they mean "we used 20% more CPU for the same output", or "we could utilize the CPUs 20% more".