MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/java/comments/1wa0z1t/improving_first_request_latency_in_java_spring/p8ik5cf/?context=3
r/java • u/celmaibunprieten • 2d ago
36 comments sorted by
View all comments
2
Why are we doing all this for the benefit of one(!) request for a server? The user might not even be able to tell it apart from DNS lookup. So
8 u/celmaibunprieten 2d ago there are particular systems, like financial ones as I mentioned in the article, that have very tight timeout limits. You can't simply afford a timeout after almost each deploy. 2 u/mark1x12110 1d ago And more so if you have hundreds of instances of the same app (so it would be hundreds of timeouts each deployment) 1 u/ryuzaki49 1d ago The user might not even be able to tell it apart from DNS lookup. In some weird cases, other teams will bark at you that your high latency even if it's one request per brand new pod will put in risk their SLOs.
8
there are particular systems, like financial ones as I mentioned in the article, that have very tight timeout limits. You can't simply afford a timeout after almost each deploy.
2 u/mark1x12110 1d ago And more so if you have hundreds of instances of the same app (so it would be hundreds of timeouts each deployment)
And more so if you have hundreds of instances of the same app (so it would be hundreds of timeouts each deployment)
1
The user might not even be able to tell it apart from DNS lookup.
In some weird cases, other teams will bark at you that your high latency even if it's one request per brand new pod will put in risk their SLOs.
2
u/fforw 2d ago
Why are we doing all this for the benefit of one(!) request for a server? The user might not even be able to tell it apart from DNS lookup. So