[
https://issues.apache.org/jira/browse/TS-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879784#comment-13879784
]
Leif Hedstrom commented on TS-2395:
-----------------------------------
For our problem, I discovered that this causes serious problems (but not
related to the health check specifically, that was a red herring):
{code}
CONFIG proxy.config.net.listen_backlog INT 65536
{code}
Changing it to
{code}
CONFIG proxy.config.net.listen_backlog INT 65535
{code}
seems to fix our problem. Not sure what to do with this error report though, I
think I'd like to close it, I've not been able to reproduce these performance
problems with the plugin itself. Any objections?
> Healthchecks plugin using 100% of CPU
> -------------------------------------
>
> Key: TS-2395
> URL: https://issues.apache.org/jira/browse/TS-2395
> Project: Traffic Server
> Issue Type: Bug
> Components: Plugins
> Reporter: David Carlin
> Assignee: Leif Hedstrom
> Fix For: 4.2.0
>
>
> I had configured the healthchecks plugin to serve four healthchecks - they
> come in pretty frequently, it can be hundreds per second. Use of the plugin
> would peg every core to 100% in htop. Response times for the healthchecks
> were often around 4 seconds.
> The code from master was used to build the plugin.
> perf top output showed the following:
> 87.74% [kernel] [k] _spin_lock
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
