3 ms·
Is soft-shedding a good idea? You're still paying CPU time to come up with a response that is a 200, but probably won't fool the client or the user anyway. With
by euyyn 10y ago
Is soft-shedding a good idea? You're still paying CPU time to come up with a response that is a 200, but probably won't fool the client or the user anyway. Without a signal that the server is having problems with load, the retries can be more aggressive.
- toomuchtodo 10y agoThat soft response should be a 429, with the client performing exponential backoff.
- dantiberian 10y agoImagine a Netflix type service which needed to calculate a bunch of different categories to show the user. If some of them are more expensive to compute than others, those categories could be dropped, while still returning an acceptable response to the user.
- drdrey 10y agoIt makes sense if CPU time is not your most constrained resource. For instance, you might use it to avoid doing expensive remote calls.