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/03/25 17:21:17 UTC
[jira] [Updated] (TS-1268) Control cache clustering via API and
records.config for e.g. object sizes
[ https://issues.apache.org/jira/browse/TS-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-1268:
------------------------------
Fix Version/s: (was: 3.3.4)
sometime
> Control cache clustering via API and records.config for e.g. object sizes
> -------------------------------------------------------------------------
>
> Key: TS-1268
> URL: https://issues.apache.org/jira/browse/TS-1268
> Project: Traffic Server
> Issue Type: New Feature
> Components: Clustering
> Reporter: Leif Hedstrom
> Fix For: sometime
>
>
> For optimal site performance, it would make sense to let the admin / programmer control which objects should be cached on only as single node vs all (or a few nodes). For example:
> 1) Always cache all objects smaller than 32KB on all cache nodes.
> 2) Cache all objects of content type text/html on all nodes.
> Ideally, we'd have both TSAPI's as well as records.config or cluster configs for the common cases. This gives the user of a cluster finer control of performance tradeoffs between storage vs latency / network congestion.
--
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