bryancall commented on issue #8693: URL: https://github.com/apache/trafficserver/issues/8693#issuecomment-4827449674
Apache Traffic Server still has no built-in cache storage tiering: there is no mechanism in the cache to keep hot objects on fast media (NVDIMM or persistent memory) and spill cold objects to HDD or QLC. The closest available approach remains partitioning the cache by hostname so specific domains can be assigned to specific (faster) storage, as documented at https://docs.trafficserver.apache.org/en/latest/admin-guide/storage/index.en.html. The community experiment that explored this (the devdax branch) depended on https://github.com/apache/trafficserver/pull/8534, which has since been closed without merging, and the original requester noted they moved off Optane and shifted to a more open-ended QLC SSD tuning idea that never produced a concrete proposal or pull request. With no actionable scope, no associated change in progress, and the issue auto-marked stale twice, I am closing this. If there is interest in real cache tiering with a concrete design, please open a fresh issue (or a design proposal) describing the intended tiering policy, and we can scope it from there. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
