[
https://issues.apache.org/jira/browse/TS-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999717#comment-12999717
]
Bryan Call commented on TS-678:
-------------------------------
I was talking to Leif about this tonight and how a group at Yahoo! found a
problem with this. Here is the graph with the delay at 20ms:
http://people.apache.org/~bcall/no-store_latency_plot.gif
Here is a graph after making it a 2ms delay:
http://people.apache.org/~bcall/fixed_latency_plot.gif
> Should we reduce MUTEX_RETRY_DELAY ?
> ------------------------------------
>
> Key: TS-678
> URL: https://issues.apache.org/jira/browse/TS-678
> Project: Traffic Server
> Issue Type: Improvement
> Reporter: Leif Hedstrom
> Fix For: 2.1.6
>
>
> We have a define
> #define MUTEX_RETRY_DELAY HRTIME_MSECONDS(20)
> which might be overly long? A suggestion was to set it to 11ms. bcall reports
> this being an issue with the old code base as well.
> Long term (post v3.0) I believe John is considering changing several of these
> locks in cache (and perhaps other areas) to be small critical sections, and
> just plain locks (and not try-locks). So it's probably not wortwhile for v3.0
> to spend significant time on the existing code (hence the quick and dirty
> reduction in the delay).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
