3 ms·
That is obvious. What is less obvious is how much memory you can waste for the internal representation. I would expect that the memory footprint of a well-des
by scscsc 17y ago
That is obvious. What is less obvious is how much memory you can waste for the internal representation. I would expect that the memory footprint of a well-designed browser should be dominated roughly by the download size (w/out taking into account the javascript code, which could keep a lot of state around).
- phillmv 17y ago> should be dominated roughly by the download size Well, judging by the graphs in the linked article this is clearly something that every browser vendor experiences. I imagine that the trade off in speedy page rendering is having a lot of memory intensive data structures. It's prolly more complicated than we give them credit for. I've never liked the griping about memory use - if you're not swapping out to disk then you're perfectly fine. I'm much more concerned with having firefox occupying a whole core if I leave it unattended with too many js intensive tabs open.