You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Phil Sorber (JIRA)" <ji...@apache.org> on 2016/11/02 23:01:58 UTC

[jira] [Updated] (TS-4957) Make the use of madvise() with MADV_DONTDUMP configurable

     [ https://issues.apache.org/jira/browse/TS-4957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phil Sorber updated TS-4957:
----------------------------
    Fix Version/s: 6.2.1

> 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
>             Fix For: 6.2.1, 7.1.0
>
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> 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)