4 ms·
I strongly disagree. If you just "visit a few sites", you'll almost certainly find something you can optimize, but you have no way of knowing how significant it
by scottlamb 2y ago
I strongly disagree. If you just "visit a few sites", you'll almost certainly find something you can optimize, but you have no way of knowing how significant it is in terms of how many sites/user/visits it affects, how its performance impact compares to say decreasing CPU cache pressure, etc. Telemetry can answer this stuff, and it can be both lightweight and accurate. I'm a big fan of looking at actual performance data (though I've mostly worked on the server side where gathering it isn't as controversial).
The goal isn't (shouldn't be) to just find a bunch of things to optimize but instead to achieve the best balance between complexity and the experience for the vast majority of users given limited engineering resources.
- eviks 2y agoWhy wound you visit a "few sites" when you can visit thousands? > you have no way of knowing how significant it is in terms of how many sites/user/visits it affects The way of knowing is getting site visiting statistics > I'm a big fan of looking at actual performance data And you'd be looking at exactly that - actual performance data on representative hardware on representative websites, but with more flexibility and more data available given the fact both parts are yours and you can collect anything without any privacy concerns
- scottlamb 2y ago> Why wound you visit a "few sites" when you can visit thousands? A "few sites" was a quote from your earlier comment. [1] You're moving the bar. Perhaps you're seeing it isn't quite as easy as you first thought to do a good job with this. [1] https://news.ycombinator.com/item?id=40570930 https://news.ycombinator.com/item?id=40570930