| 1 |
Den 20. okt. 2018 11:08, skrev Mick: |
| 2 |
> On Saturday, 20 October 2018 05:13:13 BST Andrew Udvare wrote: |
| 3 |
>>> On 2018-10-19, at 23:24, Alan Grimes <ALONZOTG@×××××××.net> wrote: |
| 4 |
>>> |
| 5 |
>>> How do I do this? |
| 6 |
>> Cgroups were sort of invented for this reason. Yes it requires Systemd. |
| 7 |
> No, I don't think systemd is obligatory, although it may be for archlinux? |
| 8 |
> |
| 9 |
> |
| 10 |
>> https://wiki.archlinux.org/index.php/cgroups |
| 11 |
>> |
| 12 |
>> I too have 32 GiB of RAM and I'm curious how Chromium acts under a |
| 13 |
>> constrained environment, or what limits can be placed especially on the |
| 14 |
>> CPU. In my experience using Chrome inside VMs, it acts very poorly. |
| 15 |
> Have a look here instead for the Gentoo alternative: |
| 16 |
> |
| 17 |
> https://wiki.gentoo.org/wiki/OpenRC/CGroups |
| 18 |
> |
| 19 |
"support for userlevel cgroups" is on the list of possible improvements |
| 20 |
there. This means some reading and manual setup to limit your browser |
| 21 |
processes. Definitely doable though. |
| 22 |
Start with turning on CGroups in /etc/rc.conf, and take it from there. |
Archives