You are not logged in.

#1 2022-06-20 22:07:32

ShaunKL
Member
Registered: 2022-06-20
Posts: 1

Understanding vm.max_map_count and the Vector Server Process

In my efforts to troubleshoot a game crash I ran across a command on ProtonDB having the user run variations of: [sudo sysctl -w vm.max_map_count=x]. Looking further into the command it "changes the amount of map areas for the Vector Server process", which is only translating to me so far as something to do with memory/virtual memory allocation.

According to the above link, my map count should be roughly 127,574 to match my 16,329,564 kB of RAM (1:128). However, currently my system is only set to 65,530.

Why are my maps set to half of what they should be, and what didn't happen for them to be correctly set, or is this the case of a game needing some exotic memory setup that is detrimental to desktop use?

Thank you for any education you can provide on this subject.

Offline

#2 2022-06-20 22:28:59

loqs
Member
Registered: 2014-03-06
Posts: 18,859

Re: Understanding vm.max_map_count and the Vector Server Process

https://github.com/torvalds/linux/blob/ … /mm.h#L178 explains why 65535-5 was chosen as the default.

Offline

Board footer

Powered by FluxBB