Re:New York Times phasing out all 3rd-party advertising data
by augustt on Tuesday May 19, 2020 @11:52AM
(#23236222)
As another datapoint, this HN page uses 56MB in Chrome for me.
[ Parent
| on HN ]
Re:New York Times phasing out all 3rd-party advertising data
by Wowfunhappy on Tuesday May 19, 2020 @12:07PM
(#23236421)
That's actually strangely high for HN, I get 7.6 MB in Firefox.
Re:New York Times phasing out all 3rd-party advertising data
by Mattwmaster58 on Tuesday May 19, 2020 @06:10PM
(#23240901)
15Mb when measured through about:performance
70Mb when measured through about:memory
I don't know why they are different.
Re:New York Times phasing out all 3rd-party advertising data
by rootusrootus on Tuesday May 19, 2020 @03:38PM
(#23239178)
17.35 MB for me in Firefox 76.0.1 on MacOS 10.15.4.
But it has been a couple hours since your comment and the other replies :)
Re:New York Times phasing out all 3rd-party advertising data
by abdullahkhalids on Tuesday May 19, 2020 @01:10PM
(#23237289)
I have 10.4 MB on firefox and, on Chrome is 33 MB.
Re:New York Times phasing out all 3rd-party advertising data
by jeltz on Tuesday May 19, 2020 @12:18PM
(#23236609)
I get 11.1 MB in Firefox.
Re:New York Times phasing out all 3rd-party advertising data
by OJFord on Tuesday May 19, 2020 @01:05PM
(#23237223)
M? Are you sure?
I get a 58kB HTML document, plus 2kB each CSS & JS, 3 * ~400B images, and a 7kB favicon.
Edit: Oh sorry, RAM. Leaving comment just to compare page size to RAM use for interest.
Re:New York Times phasing out all 3rd-party advertising data
by specialist on Tuesday May 19, 2020 @05:28PM
(#23240483)
Wow.
There's now ~388 comments. Source is 529kb and content 114kb (simple cut and paste of page, no markup).
Those are some impressive ratios.