2 ms·
The link has a disclaimer noting the stats are inaccurate. It links to the previous HN thread on this, in particular, a V8 dev noting the Safari stats didn't i
by refulgentis 6y ago
The link has a disclaimer noting the stats are inaccurate.
It links to the previous HN thread on this, in particular, a V8 dev noting the Safari stats didn't include _any_ of the rendering processes for _any_ tab, and their surprise that an informal benchmark with extremely surprising results wasn't checked: https://news.ycombinator.com/item?id=26186114 https://news.ycombinator.com/item?id=26186114
- jeroenhd 6y agoAs an extension to your comment, the disclaimer above the source [1] of the macrumors post, for context: This got a lot more attention than it deserves. As I'm pointing out below, it's likely the case that the system tool I used for measuring memory footprint isn't giving the full picture. It's also not a very indicative test in terms of every day use. However, I do think the reason this resonated with so many people is that most of us have heard the fans cool down when they exit Chrome. I'll see if I can find a better way to measure that. Stay tuned on @mortenjust So indeed, these statistics are unreliable at best and likely inaccurate or incomplete. They were recorded through psrecord[2] which doesn't record all the processes for Safari. [1]: https://www.flotato.com/post/memory-chrome-safari-flotato https://www.flotato.com/post/memory-chrome-safari-flotato [2]: https://github.com/astrofrog/psrecord https://github.com/astrofrog/psrecord
- deleted 6y ago[deleted]