Re: [whatwg/dom] Declarative Shadow DOM (#831)

By the way, you should also serve this content over HTTP/2 and push the relevant scripts.

I expect there will be also interaction between the network latency, bandwidth, & device’s raw computing power.

For example, in a low latency, low bandwidth, high computing power situation, I’d expect non-SSR solution to be faster because it sends the smaller amount of bytes and the heavy lifting is done in the client side where we have ample computing power. You might be surprised how often fast phone like iPhone 7’s CPU sits idle waiting for network payload to arrive during a page load. Counterintuitively, doing more work in CPU sometimes result in the faster overall throughout because CPU doesn’t get throttled and more things at processed at once without costing much in power consumption.

On the other hand, in high latency, high bandwidth, low computing power situation, I’d expect SSR to be faster because the increase in the network payload doesn’t matter that much after gzip (although very low end CPU may suffer from uncompressing a lot of content).

All these scenarios need to be thoroughly tested before any concrete Perf claim can be made.

Web page load performance is one of the most complicated topic imaginable, and there are so many things that have unintuitive interactions with one another.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/831#issuecomment-597423722