3 ms·
But you can cache the whole server side page and the cost is once. Whereas if you have the client side do the render then every client wears the cost.
by gonzo41 2y ago
But you can cache the whole server side page and the cost is once. Whereas if you have the client side do the render then every client wears the cost.
- iknowstuff 2y agoYou usually can't because of users who are signed in needing slightly different pages etc.
- bdcravens 2y agoWhile not as fast as a purely client cached page, the server can selectively cache content, even when some bits of the page are dynamic.
- asynchronous 2y agoWe can also cache some of the dynamic JavaScript, depending on the scenario but your point stands.
- bdcravens 2y agoWhich becomes a far more important issue when dealing with bandwidth or CPU constrained devices, or artificially imposed constraints due to data usage costs.
- Aeolun 2y agoThat’s your generation that happens once. The browser still needs to render it. Sure, rendering it on the client may cost the client a bit more, but the client generally has the computational power to spare.