[
https://issues.apache.org/jira/browse/TS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830714#comment-13830714
]
Leif Hedstrom commented on TS-1822:
-----------------------------------
Then what does it do? It's unclear to me now what exactly it does
("simultaneously" ?) Is it possible that this changed in behavior since ~2007 ?
{code}
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.
{code}
> 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: James Peach
> Fix For: 6.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.1#6144)
