[DOCS-6174] Add vm.max_map_count to Production Checklist Created: 10/Sep/15 Updated: 30/Oct/23 Resolved: 27/Sep/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 4 years, 19 weeks, 5 days ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
|
Each connection requires a thread, and each thread requires (at least) two Linux kernel page "maps" (one for the stack, and one for thread-local storage, I believe). The sysctl tunable vm.max_map_count is the maximum number of such maps that any process on the system can have. This means that the maximum number of connections is limited to at most half vm.max_map_count (less in general because of mmapped files and/or other maps that might be needed). Thus the sysctl vm.max_map_count should be added to the list of other sysctl tunabled in the Production Checklist, along with a suggested "good starting point" of 65535. (It might also help to clarify that these are sysctl settings.) |
| Comments |
| Comment by Kay Kim (Inactive) [ 27/Sep/19 ] |
|
Just doing housekeeping as we merged the commit. |
| Comment by Githook User [ 09/Mar/18 ] |
|
Author: {'email': 'qinhuili@gmail.com', 'name': 'lindaqin', 'username': 'lindaqin'}Message: |
| Comment by Githook User [ 09/Mar/18 ] |
|
Author: {'email': 'qinhuili@gmail.com', 'name': 'lindaqin', 'username': 'lindaqin'}Message: |