13 ms·
To a first approximation, you can do all your heavy-cpu computation on the server and have the client be a close-to-dumb terminal or you can have the server do
by shadowgovt 6y ago
To a first approximation, you can do all your heavy-cpu computation on the server and have the client be a close-to-dumb terminal or you can have the server do some preprocessing and the client do some postprocessing.
One spreads the load over CPUs better.
- TeMPOraL 6y ago> One spreads the load over CPUs better. Better for companies running high-powered servers with economic benefits of scale, or for users running low-end devices? This is just dumping an externality. Also, arguably, most performance issues of SPAs don't come from business-relevant calculations being slow. It comes from scaffolding, gratuitous, and bunch of other overhead that would not happen at all, server-side.
- shadowgovt 6y agoThe end user is also often paying for bandwidth, and doing local computation locally saves that cost.
- TeMPOraL 6y agoYet somehow all these locally-computed sites end up being much more bandwidth-demanding than old-school sites. Shouldn't be like this, but that's how it ended up working in practice.