- when the browser is not in the visible workspace, chromium's cpu usage actually goes to 0 whilst firefox's usually oscilates around 5%
- every new window costs 30mb of ram for chromium and 100mb for firefox
- this one is weird, but when lightly using firefox while overall ram usage spilled well into swap, often after some time terminal emulator process will get swapped-out as if firefox eventually touched memory used by every tab sitting in the background
- when the browser is not in the visible workspace, chromium's cpu usage actually goes to 0 whilst firefox's usually oscilates around 5%
- every new window costs 30mb of ram for chromium and 100mb for firefox
- this one is weird, but when lightly using firefox while overall ram usage spilled well into swap, often after some time terminal emulator process will get swapped-out as if firefox eventually touched memory used by every tab sitting in the background