Re: [arch-announce] Increasing the default vm.max_map_count value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Sun, 2024-04-07 at 18:12 +0000, Arch Linux: Recent news updates:
Robin Candau wrote:
> The [vm.max_map_count][1] paramater will be increased from the
> default `65530` value to `1048576`.

> 
> This change should help address performance, crash or start-up issues
> for a number of memory intensive applications, 

Performance improvement is unlikely but could allow something to run
that otherwise would not. 
The lkml comment [1] is worth a read and includes :

    "To be clear, what you are doing here is akin to adding more memory
to
   your system when there is a memory leak.  This is not the solution
you
   should be pushing.  Ironically, this is using more memory and
performing
   worse than it should.  At best, the limit increase is a workaround
for
   buggy programs."

As Robin said, setting the max higher is probably benign - and only
impacts a system running the problematic software (games).

Nonetheless, it is very simple to change it to whatever value you want
with your own prefs dropped into /etc/sysctl.d/xxx.conf

gene


 [1] https://lore.kernel.org/lkml/566168554.272637693.1710968734203.Jav
aMail.root@zimbra54-
e10.priv.proxad.net/T/#m1905a48f415bc6e8069a8fe53dec44bc311571f2


-- 
Gene

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux