[
https://issues.apache.org/jira/browse/TS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431188#comment-15431188
]
Phil Sorber commented on TS-1822:
---------------------------------
>From the {{mallopt}} man page:
{noformat}
M_MMAP_MAX
This parameter specifies the maximum number of allocation
requests that may be simultaneously serviced using mmap(2).
This parameter exists because some systems have a limited
number of internal tables for use by mmap(2), and using more
than a few of them may degrade performance.
The default value is 65,536, a value which has no special
significance and which servers only as a safeguard. Setting
this parameter to 0 disables the use of mmap(2) for servicing
large allocation requests.
{noformat}
So it seems like it still matters simply because of the implementation. We
mostly do our own large allocations via {{mmap}} directly, but we still have a
lot of {{malloc}}'s floating around. I think that [[email protected]]'s
suggestion is a good one and to just hardcode it.
> Do we still need proxy.config.system.mmap_max ?
> -----------------------------------------------
>
> Key: TS-1822
> URL: https://issues.apache.org/jira/browse/TS-1822
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Reporter: Leif Hedstrom
> Assignee: Phil Sorber
> Labels: incompatible
> Fix For: 7.0.0
>
>
> A long time ago, we added proxy.config.system.mmap_max to let the
> traffic_server increase the max number of mmap segments that we want to use.
> We currently set this to 2MM.
> I'm wondering, do we really need this still ?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
