[
https://issues.apache.org/jira/browse/TS-4957?focusedWorklogId=30873&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-30873
]
ASF GitHub Bot logged work on TS-4957:
--------------------------------------
Author: ASF GitHub Bot
Created on: 19/Oct/16 13:13
Start Date: 19/Oct/16 13:13
Worklog Time Spent: 10m
Work Description: Github user jrushford commented on the issue:
https://github.com/apache/trafficserver/pull/1097
Thanks @jpeach. FWIW, this patch is originally from TS-3417 and @PSUdaemon
and I dug it up after we discovered we had a problem with madvise() and to fix,
required deploying a new rpm to 1300+ proxies. I'm okay with the name change
and will make it if @zwoop and @PSUdaemon agree.
Issue Time Tracking
-------------------
Worklog Id: (was: 30873)
Time Spent: 10m
Remaining Estimate: 0h
> 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: sometime
>
> Time Spent: 10m
> 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)
