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 2010/05/26 01:31:37 UTC
[jira] Created: (TS-374) Potentially eliminate lock contention on
HostDB
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
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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-374) Potentially eliminate lock contention on
HostDB
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-374:
-----------------------------
Fix Version/s: 2.3.0
> 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
> Fix For: 2.3.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.