Hi guys,

Just wanted to enquire about cache. More importantly, how does it interact with the array.

My array is all set up now and working really well. I'm very happy with it.

 

On my 'MAIN' tab of the Web GUI, I've noticed that my cache %'s never move at all. I have set up a shares for the cache. I've also enabled the cache only option to that share. But I just never, ever, see it working at all. I have included a photo for you to see what I mean. So my question is:

 

1. From everything I've read on the Limetech website, the cache is automatically used once you assign the cache drive. Am I reading that correctly? Have I skipped any settings? The read/writes show that it is literally inactive.

 

I have only been using this server so far as a media device (plex) and it's working brilliantly. I have assigned the transcoding to be done in the /tmp folder, instead of the SSD. Is this why I'm seeing no activity on the SSD?

 

Enjoy your weekend folks

Kind regards,

Morten

In principle use of the cache should be automatic once things are set up correctly.

 

Perhaps you can provide a screenshot of the cache drive settings and the share settings for a share that should be using the cache.    Also going to Tools->diagnostics and posting the file created from their provides all the information to help with diagnosing any issues you are having.

OK.... thanks itimpi, that sounds like what I expected.

 

In the shares, if the cache box is set to 'use cache', then the drive will be used, provided there is space. Any overflow will be written/read from array.

If the 'use only cache' is selected, then everything is written and read from that drive, correct?

 

 

if use cache is active, files written to the share will be written to the cache. files will be read from cache, if they are currently on the cache drive.

the cache drives main purpose is to accelerate writes.

the mover then moves the files to the array. (you can set the intervall in the scheduler settings. i think most people move daily during the night)

 

shares with cache only are ignored by the mover, so files get written to the cache and will stay on the cache. (mostly used for application data from docker apps and virtual machines)

Sweet.... makes sense. Many thanks Benni