Re: F39 proposal: Increase vm.max_map_count value (System-Wide Change proposal)

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

 



Interesting that this came up.  I was just talking to someone else about this the other day.  From what I understand, that sysctl affects the max number of memory map areas a process can have, i.e. contiguous reserved memory.  For a game that's great because it can pack more into memory and decrease disk IO.  
My guess is that this is really not an issue for the Steam Deck because realistically it will only be doing a few things at once... Basic system, Steam Client, and the Game running.
How this would affect memory performance on a workstation or server with much more running concurrently, is something I can't really speak to, but I would guess there's a point where increasing it could cause issues depending on total memory available and how many processes are getting memory reservations from the kernel. 
At first glance it should be relatively easy to get at least a simple baseline check on a busy workstation/server that isn't massively loaded with RAM.  A system that starts to run into memory pressure during heavy use should reveal if this change causes problems under the same workload.



On Mon, Apr 24, 2023 at 1:13 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
A few questions:

* Could we perhaps try and get upstream to adjust this higher?

* Is there any description/docs on what happens when this value is too
low? do games error in a particular way?

* Is there any adverse impact increasing this? More memory used?

Thanks for putting this together.

kevin
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux