I don't know for sure, but I don't think a RAM cache only solution works for them. They have a very large amount of content, and (I think?) 20-40TB of disk in each cache box. This proposal is a way to control (via configs and plugins) which contents has priority. It's a neat solution IMO, but not as generic as
TS-745. In either case, i always felt it lacking that you can't control which disks a "volume" occupies, I can see plenty of use cases where I want to use expensive (say 15k SAS or SSD) for some content, and less expensive disks for content I care less about (e.g. where high latencies is fine).
I understand the complication of combining
TS-745 and TS-1728. This is also why I'm being a jerk and insisting that we make one config format for all disk / tiered caches control. Even if it means that for example tiered caching takes precedence over the volume identification, it's still a hell of lot clearer where this gets configured.
Phil, James, Jan, John? Any thoughts on this?