2 ms·
Obviously you need to weigh the gains vs the development time required for adding and maintaining this, as with anything. In terms of the user experience, if t
by wahnfrieden 15y ago
Obviously you need to weigh the gains vs the development time required for adding and maintaining this, as with anything.
In terms of the user experience, if the perf gains are small enough, then the chance that the user tries to exit while a request is in-progress should be slim, so interrupting their exit is fine as an edge case, and the gains in responsiveness should be weighed against your core user or business metrics - several hundred ms extra delay per action can have a significantly negative impact.
If the gains are large enough that the user is likely to interrupt something when exiting, then blocking the entire UI for each request is a terrible experience and you need to do something about it anyway.