4 ms·

It’s quite clearly a lot. Just not as much as you.

• NavinF 3y ago
  I meant that for a modern machine 1500 is nowhere close to the maximum amount you can have before TLB misses (and later page faults) slow down the entire machine. If a machine with similar specs can't handle that many tabs, something is misconfigured. Eg maybe memory timings are way too conservative or the wrong power profile is in use.
  • astrange 3y ago
    Remember a website can do anything it wants, and that includes leaking 32GB memory. Browsers have been implementing background tab killing recently though, so just because you have a tab doesn't mean the process is actually backing it anymore.
    • NavinF 3y ago
      I've seen the occasional memory leak from Youtube and Twitter, but only once a month. Not a big deal since I try to reboot for security updates every 3-6 months anyway.
  • brigade 3y ago
    1500 tabs easily touches enough RAM that average computers will keep swapping if that's actually your working set. Which is why any good browser should be completely freezing tabs that haven't been active in a while so their memory can remain swapped out, or even completely unloading them. Though, 1500 tabs in one window is beyond the point at which it impacts Safari's responsiveness, but that's completely unrelated to the contents of the tabs and is instead the fault of taking way too long to update every NSView in the tab bar.