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, particularly for (but not limited to) [some Windows games][2] played through Wine/Steam Proton. Overall, end users should have a smoother experience out of the box with no expressed concerns about potential downsides in [the related proposal on arch-dev-public mailing list][3]. This `vm.max_map_count` increase is introduced in the `2024.04.07-1` release of the [filesystem package][4] and will be effective right after the upgrade. Before upgrading, in case you are already setting your own value for that parameter in a `sysctl.d` configuration file, either remove it (to switch to the new default value) or make sure your configuration file will be read [with a higher priority][5] than the `/usr/lib/sysctl.d/10-arch.conf` file (to supersede the new default value). [1]: https://docs.kernel.org/admin-guide/sysctl/vm.html#max-map-count [2]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057792/comments/5 [3]: https://lists.archlinux.org/archives/list/arch-dev-pub...@lists.archlinux.org/thread/5GU7ZUFI25T2IRXIQ62YYERQKIPE3U6E/ [4]: https://archlinux.org/packages/core/any/filesystem/ [5]: https://man.archlinux.org/man/sysctl.8#SYSTEM_FILE_PRECEDENCE URL: https://archlinux.org/news/increasing-the-default-vmmax_map_count-value/
