On 01/04/2020 21:29, James Knott wrote:
I'm going my both System Monitor and Top.
I consider using swapon -s to be authoritative :-)
The thing is no matter how much swap is used, it runs fine, then suddenly the CPUs max out and the system bogs down.
There isa a fundamental difference between firefox and Chromium and and a side effect of how they handle data. Firstly, FF is a single process therefore a single allocation in the process table, whereas Chromium has a process per page. In terms of code &mapping that doesn't make any difference, but the way scheduling works and the way paging allocation buffer tables work it does. Sometimes, I suspect some long-lived images, Linux can re-map pages into BigPages. but these are unswapable. To much of that and the system will og down. I'm sure this is tunable. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org