3 ms·
A better benchmark is done through the web browser inspector (network tab or performance tab). In the network tab I got (cache disabled) Github 158 request
by skydhash 11mo ago
A better benchmark is done through the web browser inspector (network tab or performance tab). In the network tab I got (cache disabled)
Github
158 requests
15.56 MB (11.28 MB transferred)
Finish in 8.39s
Dom loaded in 2.46s
Load 6.95s
Codeberg
9 requests
1.94 MB (533.85 KB transferred)
Finish in 3.58s
Dom loaded in 3.21s
Load 3.31s
- nromiun 11mo agoI guess Github uses a lot of cache vs Codeberg.
- kragen 11mo agoI think you read that backwards. In skydhash's test, Codeberg's data was 72% cached, and GitHub's data was 28% cached. Maybe you meant that GitHub's cached 4.28MB was, in absolute terms, more than Codeberg's cached 1.41MB?
- nromiun 11mo agoYeah, that is what I meant. It looks like Github's strategy is to push all the initial data they need to cache, to optimize subsequent requests.
- skydhash 11mo agoSome parts of Github are SPA island, which is why the DOM load fast, but then it has to wait for the JavaScript files and the request made by those files. Codeberg can be used with JavaScript disabled and you don’t have that much extra requests (almost everything is rendered serverside). The transferred part is for the gzipped transfer. That makes sense if the bulk of the data is HTML (I have not checked). I’ve disabled the cache for the network requests.
- kragen 11mo agoOh, thank you for the correction. That was a dumb mistake on my part.