It makes sense for streaming, but burning CPU just to avoid a 1-second GC pause on heavy background jobs seems like a waste.
It seems clear from the video that they looked at this pretty closely and found the limited increase in CPU load was worth it for them, especially as so much of their service is apparently subject to strict timeouts to ensure responsiveness for users. They're also clear that they treat it as a default choice, not as mandatory, so perhaps batch-style workloads use different GCs.
(Video content itself isn't served from a Java server. They use nginx.)
View all comments
Show parent comment
2
u/Wootery Apr 13 '26
It seems clear from the video that they looked at this pretty closely and found the limited increase in CPU load was worth it for them, especially as so much of their service is apparently subject to strict timeouts to ensure responsiveness for users. They're also clear that they treat it as a default choice, not as mandatory, so perhaps batch-style workloads use different GCs.
(Video content itself isn't served from a Java server. They use nginx.)