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

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/12/27 01:35:52 UTC

[jira] [Commented] (TS-1365) specifying -t option doesn't seem to have the desired effect on epoll timeout

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

Leif Hedstrom commented on TS-1365:
-----------------------------------

I have a patch to make both this and TS-1336 work nicely together. Specifically, it'll assure that specifying -t (or the new records.config option) will not cause this degenerate behavior.

> specifying -t option doesn't seem to have the desired effect on epoll timeout
> -----------------------------------------------------------------------------
>
>                 Key: TS-1365
>                 URL: https://issues.apache.org/jira/browse/TS-1365
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: Igor Galić
>            Assignee: Leif Hedstrom
>             Fix For: 4.2.0
>
>
> In normal operations we see {{traffic_server}} using around 2.5 % while idle.
> The assumption is that it's doing a lot of {{epoll_wait()}} - increasing the timeout (~10000) with {{-t}} *increased* the CPU load. Setting it to the default (10) has no affect - as expected. Setting it to 0 gives us 100% CPU usage (as semi-expected).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)