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

Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/16 20:05:16 UTC

[jira] [Commented] (TS-374) Potentially eliminate lock contention on HostDB

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

ASF subversion and git services commented on TS-374:
----------------------------------------------------

Commit ba3b7d023577e33a93cc038ad64f41781633424a in branch refs/heads/master from Bryan Call <bc...@apache.org>
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=ba3b7d0 ]

TS-374 Changed the retry to use HOST_DB_RETRY_PERIOD (2ms) and switch the
locking from a trylock to a lock.

                
> Potentially eliminate lock contention on HostDB
> -----------------------------------------------
>
>                 Key: TS-374
>                 URL: https://issues.apache.org/jira/browse/TS-374
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Leif Hedstrom
>            Assignee: Bryan Call
>             Fix For: 3.3.3
>
>
> When using as a reverse proxy, when a single (or very few) HostDB entries are under "pressure", the try-lock there could cause us to reschedule. John suggests we look at this as a first step towards reducing latencies under high load, by avoiding holding the lock over multiple callbacks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira