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 2013/05/03 19:24:17 UTC
[jira] [Updated] (TS-149) Split ram and disk cache hit response
times into separate metrics
[ https://issues.apache.org/jira/browse/TS-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-149:
-----------------------------
Labels: A (was: )
> Split ram and disk cache hit response times into separate metrics
> -----------------------------------------------------------------
>
> Key: TS-149
> URL: https://issues.apache.org/jira/browse/TS-149
> Project: Traffic Server
> Issue Type: New Feature
> Components: Cache
> Reporter: Anirban
> Priority: Minor
> Labels: A
> Fix For: 3.5.0
>
>
> Split ram and disk cache hit response times into separate metrics
> Original description
> by Stephen Bisordi from Yahoo
> It appears that the response time for ram cache hits and disk cache hits is captured as a single metric
> (transaction_totaltime.hit_fresh). Would it be possible to split this into two separate metrics, or to add a ram cache
> hit result code to the log to differentiate between ram and disk hits (similar to Squid's TCP_MEM_HIT)?
> This change would allow for quicker troubleshooting of certain issues such as poor disk performance.
>
--
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