You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "John Plevyak (JIRA)" <ji...@apache.org> on 2010/05/06 23:44:48 UTC

[jira] Commented: (TS-337) Cache Replacement Algorithm plug-in API

    [ https://issues.apache.org/jira/browse/TS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864940#action_12864940 ] 

John Plevyak commented on TS-337:
---------------------------------

The Ram Cache now has a pluggable interface.

The disk cache is a cyclone with optional pinning and evacuation like a log based file system.  It doesn't make a great deal of sense to talk about a puggable replacement policy for such a cache since it can't simply reclaim any object it wants.

Instead there have been proposals to make the entire cache pluggable and perhaps in one or more of these there could be a pluggable replacement policy, perhaps even with a compatible interface.

Perhaps this should be a feature under that much larger design issue and moved to the wiki?

If so, this bug should be closed now that the Ram Cache is pluggable.

> Cache Replacement Algorithm plug-in API
> ---------------------------------------
>
>                 Key: TS-337
>                 URL: https://issues.apache.org/jira/browse/TS-337
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Cache
>    Affects Versions: 2.0.0
>            Reporter: Mark Nottingham
>
> New cache replacement algorithms are often proposed, and often it's not a "one size fits all" problem; different workloads require different approaches.
> To facilitate this, TS should have a pluggable cache replacement policy API, both for the memory and disk cache.
> Squid has done this to good effect; see
>   http://www.squid-cache.org/cgi-bin/cvsweb.cgi/squid/src/repl/

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.