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 2016/04/08 20:02:25 UTC
[jira] [Updated] (TS-2992) EThread schedule fast_signal default
[ https://issues.apache.org/jira/browse/TS-2992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-2992:
------------------------------
Fix Version/s: (was: 6.2.0)
7.0.0
> EThread schedule fast_signal default
> ------------------------------------
>
> Key: TS-2992
> URL: https://issues.apache.org/jira/browse/TS-2992
> Project: Traffic Server
> Issue Type: Task
> Components: Core
> Reporter: Otto van der Schaaf
> Assignee: Alan M. Carroll
> Labels: review
> Fix For: 7.0.0
>
> Attachments: ethread.patch
>
>
> For ats_speed, changing the fast_signal argument's default from false to true in I_EThread::schedule helped improve latency when scheduling an event from an external thread pool (up to 5 ms per scheduled operation).
> This ticket at least documents this fact, and can perhaps serve as a discussion point. Perhaps it's worth it to make a setting out of this hard coded default.
> I'm not sure that setting fast_signal to true would be a good idea in general, as there probably is a cost to it. It was working fine for us though, and considering ats_speed's cause (leaning towards favoring user agents) I think it can sometimes be beneficial.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)