The UI stalling behavior doesn't seem to be dependant on hitting RAM or CPU bottlenecks, since when it happens I still have idle and under-used cores, and ram is not close to full. As I understand it, Chrome stops giving you "one tab per process" once you pass a certain number of tabs and I'm guessing that's where the problem comes from.
My test system is smaller than yours: 8 cores and 8G RAM, but that ought to be sufficient out to at least 100 tabs.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds