[jira] [Comment Edited] (TS-1822) Do we still need proxy.config.system.mmap_max ?

["James Peach (JIRA)" <ji...@apache.org>]

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

James Peach edited comment on TS-1822 at 11/11/14 5:32 PM:
-----------------------------------------------------------

This seems to be getting way off track. {{proxy.config.system.mmap_max}} does not set any sysctls. It sets the {{M_MMAP_MAX}} malloc option when using the glibc allocator. For what that does, see http://man7.org/linux/man-pages/man3/mallopt.3.html.

My view is that we should just remove this or hardcode the value. I can't imagine an operator be able to sensibly tune this.




was (Author: jamespeach):
This seems to be gerund way off track. {{proxy.config.system.mmap_max}} does not set any sysctls. It sets the {{M_MMAP_MAX}} malloc option when using the glibc allocator. For what that does, see http://man7.org/linux/man-pages/man3/mallopt.3.html.

My view is that we should just remove this or hardcode the value. I can't imagine an operator be able to sensibly tune this.



> 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: compatibility
>             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.3.4#6332)