[ 
https://issues.apache.org/jira/browse/TS-1822?focusedWorklogId=26816&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26816
 ]

ASF GitHub Bot logged work on TS-1822:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Aug/16 21:14
            Start Date: 22/Aug/16 21:14
    Worklog Time Spent: 10m 
      Work Description: Github user zwoop commented on the issue:

    https://github.com/apache/trafficserver/pull/892
  
    Ship it.
    
    :+1:


Issue Time Tracking
-------------------

    Worklog Id:     (was: 26816)
    Time Spent: 40m  (was: 0.5h)

> 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: 40m
>  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)

Reply via email to