Am 24/08/2022 um 10:26 schrieb Fiona Ebner:
> Am 24.08.22 um 01:56 schrieb Matt Corallo:
>>
>>
>> On 8/19/22 6:08 AM, Fiona Ebner wrote:
>>> Hi,
>>>
>>> On 16.08.22 05:49, Matt Corallo wrote:
Proxmox documentation describes the default CPU weight as 1024 in
numerous places. However, when
Am 24.08.22 um 01:56 schrieb Matt Corallo:
>
>
> On 8/19/22 6:08 AM, Fiona Ebner wrote:
>> Hi,
>>
>> On 16.08.22 05:49, Matt Corallo wrote:
>>> Proxmox documentation describes the default CPU weight as 1024 in
>>> numerous places. However, when unset, the Linux default CGROUP
>>> weight is 100.
--- Begin Message ---
On 8/19/22 6:08 AM, Fiona Ebner wrote:
Hi,
On 16.08.22 05:49, Matt Corallo wrote:
Proxmox documentation describes the default CPU weight as 1024 in
numerous places. However, when unset, the Linux default CGROUP
weight is 100.
I'd rather update the documentation in
Hi,
On 16.08.22 05:49, Matt Corallo wrote:
> Proxmox documentation describes the default CPU weight as 1024 in
> numerous places. However, when unset, the Linux default CGROUP
> weight is 100.
>
I'd rather update the documentation in all places, because most likely
it just wasn't adapted to
Sorry, replied to the wrong mail. Please ignore this.
On 19.08.22 12:01, Fiona Ebner wrote:
> Hi,
>
> On 16.08.22 05:49, Matt Corallo wrote:
>> Proxmox documentation describes the default CPU weight as 1024 in
>> numerous places. However, when unset, the Linux default CGROUP
>> weight is 100.
>>
Hi,
On 16.08.22 05:49, Matt Corallo wrote:
> Proxmox documentation describes the default CPU weight as 1024 in
> numerous places. However, when unset, the Linux default CGROUP
> weight is 100.
>
I'm not saying increasing the timeout can't be worth it, but I haven't
seen many reports about the
--- Begin Message ---
Proxmox documentation describes the default CPU weight as 1024 in
numerous places. However, when unset, the Linux default CGROUP
weight is 100.
This simply always writes an `lxc.cgroup2.cpu.weight` option to the
LXC config file, defaulting to 1024 instead of omitting the