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 2015/04/05 05:13:33 UTC
[jira] [Updated] (TS-3496) Should we retune
proxy.config.cache.mutex_retry_delay ?
[ https://issues.apache.org/jira/browse/TS-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-3496:
------------------------------
Fix Version/s: 6.0.0
> Should we retune proxy.config.cache.mutex_retry_delay ?
> -------------------------------------------------------
>
> Key: TS-3496
> URL: https://issues.apache.org/jira/browse/TS-3496
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache, Configuration
> Reporter: Leif Hedstrom
> Fix For: 6.0.0
>
>
> I'm starting to wonder that I might have done a boo-boo, and set this default too short? Should we bump proxy.config.cache.mutex_retry_delay from 2 to 10 by default? [~amc]
> I'm working on a different patch too, making more hardcoded defines configurable, which also introduces a feature to normalize these retry delays based on the number of ticks the system has (100 on Linux, 128 on FreeBSD). So we could auto-scale this to the closest multiplier of these (so, 10 on Linux, 8 on FreeBSD).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)