[
https://issues.apache.org/jira/browse/TS-1822?focusedWorklogId=26803&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26803
]
ASF GitHub Bot logged work on TS-1822:
--------------------------------------
Author: ASF GitHub Bot
Created on: 22/Aug/16 17:36
Start Date: 22/Aug/16 17:36
Worklog Time Spent: 10m
Work Description: GitHub user PSUdaemon opened a pull request:
https://github.com/apache/trafficserver/pull/892
TS-1822: Remove proxy.config.system.mmap_max in favor of MALLOC_MMAP_…
…MAX_ environment variable.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/PSUdaemon/trafficserver ts-1822
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/892.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #892
----
commit 7a403238c02e7999676010b13fb00907bf1db285
Author: Phil Sorber <sor...@apache.org>
Date: 2016-08-22T17:34:20Z
TS-1822: Remove proxy.config.system.mmap_max in favor of MALLOC_MMAP_MAX_
environment variable.
----
Issue Time Tracking
-------------------
Worklog Id: (was: 26803)
Time Spent: 10m
Remaining Estimate: 0h
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
