or they leak memory. or a heavy request generates gc activity which impacts other requests.
i've seen site outages in large companies due to these sorts of bugs. multiple times. this is a major set of problems that you avoid by having a memory model that fits the domain (http services). php sort of did it by accident, but it works. BEAM gets this right as well.
Comments
That is not a virtue. Java (And ruby, and python, and ASP.Net) get faster when they warm up.
or they leak memory. or a heavy request generates gc activity which impacts other requests.
i've seen site outages in large companies due to these sorts of bugs. multiple times. this is a major set of problems that you avoid by having a memory model that fits the domain (http services). php sort of did it by accident, but it works. BEAM gets this right as well.
That is a possible failure mode, but if it's standard practice in the systems you're touching you've had some bad luck?