4 ms·
the best way is via CRaC (https://docs.azul.com/crac/ https://docs.azul.com/crac/) but only a few vendors support it and there’s a bit of process to get it setu
by rileymichael 7mo ago
the best way is via CRaC (https://docs.azul.com/crac/ https://docs.azul.com/crac/) but only a few vendors support it and there’s a bit of process to get it setup.
in practice, for web applications exposing some sort of `WarmupTask` abstraction in your service chassis that devs can implement will get you quite far. just delay serving traffic on new deployments until all tasks complete. that way users will never hit a cold node
- zelphirkalt 7mo agoBut then we can complain about the long start time for each instance or JVM. It is choosing a different trade-off.
- rileymichael 7mo agostart time generally isn't a huge concern for web applications (outside of serverless) since you've got the existing deployment serving traffic until its ready. if you're utilizing kubernetes, the time to create the new pods, do your typical blue-green promotion w/analysis tests etc. is already a decent chunk of time regardless of the underlying application. if you get through it in 90 seconds instead of 60, does that really matter?