7 ms·
That's wonderful! How much RAM does it need? My biggest complaint about modern browsers is that I can't load a web page in less than 64 MiB, which is more tha
by kragen 5y ago
That's wonderful! How much RAM does it need?
My biggest complaint about modern browsers is that I can't load a web page in less than 64 MiB, which is more than my entire computer had when I was running Netscape 3. The browsers are better now, but not in ways that necessarily use more memory.
- niutech 5y agoTry Ultralight web engine or K-Meleon on Goanna, they are really lightweight.
- kragen 5y agoHow much memory do they need to load this discussion thread page?
- akling 5y agoWe haven't really begun to optimize for memory usage yet, so it swings wildly depending on the content you're viewing. At this stage, we're primarily focusing on correctness and compatibility, and performance is mostly a luxury. It's an area I look forward to eventually dealing with though, as it used to be my full-time job at Apple years ago and I have many fun ideas. :^)
- kragen 5y agoWhat's a rough minimum for a page with some text on it? Are we talking about 64MiB like Chromium, WebKit, or Gecko, or more like 16KiB, 256KiB, 4MiB, or 1 GiB? I think of memory usage as being more about correctness than performance, though I know that isn't how most people see it. Trying to run a 512MiB process on a 64MiB computer, or a 512GiB process on a 64GiB computer, is just never going to run at a usable speed. Broken software is the limit as latency approaches infinity. Moreover, I've never seen someone take software that needed 1 GiB to run and modify it incrementally into software that could run in 1 MiB, though I have seen the opposite.
- akling 5y agoIf I open this HN discussion page in the browser, it currently uses 44MB of private memory. We can definitely shave a couple of megabytes off of it with some effort, but supporting the contemporary web on a 4MB budget seems infeasible.
- kragen 5y agoNice! Thanks! That's a real improvement over the existing browsers! Yeah, clearly you can't run Slack or Fecebutt in 4MiB, but there's a lot you could do. Even Lynx takes 14MB of RSS (not all private!) and 25MB of VSZ to load this discussion page, and Links is 9MB/13MB. (Neither of them produces a usable layout, but that's not because they're using a lot of memory.) The page source is 179K, links's "formatted output" of the page is 59 kB, and Firefox tells me it has 2908 HTML elements in it, so it's probably possible to render it in under a meg. I doubt anyone ever will.
- rasz 5y agohttps://get.opera.com/pub/opera/win/1218/en/ https://get.opera.com/pub/opera/win/1218/en/ Opera_1218_en_Setup_x64.exe Default portable install. 27.8MB windowed, one empty tab open 24MB minimized, one empty tab open 35MB windowed, one tab open with this thread loaded and scrolled once up and down 31MB minimized, one tab open with this thread loaded and scrolled once up and down 33MB windowed, one tab open with this thread loaded after restart 29MB minimized, one tab open with this thread loaded after restart Opera needs ~5MB to load and properly render this page, and 28MB for the rest of the browser. Btw it also gets 100/100 on http://wpt.live/acid/acid3/test.html http://wpt.live/acid/acid3/test.html :-)
- Someone 5y agoYour screen likely has gotten better in ways that necessarily use more memory: more pixels, more bit depth means larger pictures, larger font caches (because of larger characters and anti-aliasing), etc. The pages you look at also have gotten ‘better’ in ways that necessarily use more memory. I don’t think you regularly loaded megabytes of JavaScript. Finally, your browser usage likely has gotten ‘better’ in ways that necessarily use more memory. I guess you have more tabs open than you ever had in that 64 MiB.
- kragen 5y agoWhile there is something to this, and antialiased fonts and CJKV rendering are particularly beneficial, I mostly don't agree about necessarily using more memory (see https://news.ycombinator.com/item?id=30872388 https://news.ycombinator.com/item?id=30872388). We're talking about orders of magnitude more memory than the screen contents. As for JS, on most pages the only benefit of those megabytes of JavaScript is that I need to use uBlock Origin and/or Reader Mode to read what I'm actually interested in, the page jumps around at random while I'm trying to read it, Twitter tries to extort me into logging in, DoubleClick and reCaptcha can fingerprint my GPU, etc. Also, a megabyte of minified JS might reasonably compile down into a megabyte of bytecode or 4 MiB of native code, not 64 MiB or 128 MiB. JS's execution model is kind of inherently memory-hungry, though. 64 MiB is for one tab.