[
https://issues.apache.org/jira/browse/TS-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567155#comment-15567155
]
John Rushford commented on TS-4957:
-----------------------------------
In our prod, were on kernel version 2.6 and this triggered the problem
described. We've started testing Centos 7 with kernel version 3.10 but we do
not know yet if there is a problem there. In any case, we think this should be
configurable.
> Make the use of madvise() with MADV_DONTDUMP configurable.
> ----------------------------------------------------------
>
> Key: TS-4957
> URL: https://issues.apache.org/jira/browse/TS-4957
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Reporter: John Rushford
> Assignee: John Rushford
>
> We have run into problems with ATS 5.3.x when using madvise() with the
> MADV_DONTDUMP option to exclude IO buffers from core files. Under load, we
> have seen high cpu loads and very slow time to serve times when allocating IO
> buffers and marking them with this flag. We have had to disable calls to
> madvise() in ats_madvise(), rebuild and redeploy to fix this problem. We'd
> like to make the use of madvise() with the MADV_DONTDUMP option configurable.
> The PR associated with this ticket uses a patch from TS-3417 that implements
> making MADV_DONTDUMP configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
