FWIW, I use separate cache volumes to store playlist files and segment files, by modifying the cache key to include different hostnames for each kind of file. It does work well :)
Here's a sample config: hosting.config: hostname=blahblah.com volume=1 hostname=* volume=2,3,4 In my plugin, I set the cache key for playlist files (identified with file extension .m3u8), as blahblah.com/.... This makes all the playlist files go to volume 1, while the rest go to other volumes. For the original question that Daniel asked though, it should still work to create a ramdisk based volume and modifying cache key to point to that volume etc, but, I think a lot simpler approach would be to use a dynamic cache key with a query param that's unique per restart (e.g. timestamp). Thanks, Sudheer On Monday, September 28, 2015 1:53 PM, Phil Sorber <[email protected]> wrote: On Mon, Sep 28, 2015 at 2:48 PM Jeremy Payne <[email protected]> wrote: i am going to test this tonight, but are you saying that it's possible to split the cache based on some transaction condition? > > >meaning the below would be stored in ramdisk. > > >http://media.domain.com/chunk.ts > > >while the below would be stored in a generic(disk) volume. > > >http://media.domain.com/image.gif > > >again, i have yet to test, but i believe this is all driven by setting the >cache key to use the domain which is mapped to the ramdisk volume. > >if this sounds right to you, then it means i am on the right path. > > > > I know for sure you can specify what volume you want something to land on. Not sure if setting the cache key will do this for you though. Worth a shot. Also, I think was Leif was suggesting was that you turn the ram cache off in favor of a ram drive, but that will have the side effect of turning ram cache off for your non-volatile storage as well which I do not think you want. > > > > > >On Mon, Sep 28, 2015 at 3:26 PM, Leif Hedstrom <[email protected]> wrote: > > >> >>On Sep 28, 2015, at 12:37 PM, Jeremy Payne <[email protected]> wrote: >>> >>>not sure if this answers your question, but i have been thinking about >>>something similar. >>> >>>this is how i have it played out in my mind, although i havent looked at the >>>transaction points to see when host/domain is considered for volume >>>placement. >>> >>>1. create a ramdisk(or some memory based filesyetm) >>>2. map the ramdisk to store content for some domain >>> >> >> >> >>This ought to work, however, be aware that if you have ATS configured with a >>RAM cache, you will store such objects in RAM twice. If you do this, odds are >>that you are best off turning off RAM cache entirely in ATS itself (but, I’ve >>never done that, so not sure how the performance will be). >> >> >>— Leif >> >> >>3. write a lua script to change the cache key of specific requests to >>something within the ramdisk domain >>>4. the expectation is that with this change, the desired objects will be >>>found in the ramdisk volume. >>> >>> >>> >>> >>> >>>On Mon, Sep 28, 2015 at 1:20 PM, Daniel Morilha <[email protected]> wrote: >>> >>>Hi, >>>> >>>> >>>>I would like to know if ats provides any way to trick the cache and store >>>>some specific request only in RAM so when ats restarts the entry won't be >>>>there any longer. >>>> >>>> >>>>Thanks, >>>> >>>>-- >>>> >>>>Daniel Morilha ([email protected]) >>> >> >
