Locally cache metadata

[Happy2Play 9780]

2 hours ago, Statick said:

update, this setting actually gets changed back every time you restart Emby. can we please just have a way to turn this off and it stays off please - every time the cache gets cleaned out, my emby slows to a crawl due to it pulling in all the artwork over a slow VPN, when that artwork was already cached and working just fine before that happened. I never delete any content from my libraries so there's literally no reason for me to need to clear out the cache more than once a year. it's really frustrating that this can't just be adjusted with a simple setting but we have to go digging into API commands, and even then whatever setting we choose just gets replaced with the default every time it restarts anyway

I don't really follow a custom setting changing here.  I still have the same no trigger task in my /programdata/config/scheduledtask folder and task has not run in months per the api query.

Only way the triggers can change is something happened to your customized json file.  Or devs changed the taskid.

[rbjtech 5284]

I've found a solution to this issue but it involves the use of Drive Pool software - in my case Stablebit Drivepool.

I've simply configured Drivepool (File Placement Rules) to store all metadata file types (images, nfo's, bif's etc - anything that is not a large video file) to use an SSD (must be part of the pool but does not have to be dedicated) but this is actually just a pointer from the main Pool (on HDD).

In other words, I can see and use the metadata files stored 'with' the media, but they actually reside on an SSD.

Not only is this faster, but any cache refresh will not access the physical disks as it's just a logical redirect to the SSD.

Maybe an option for those using Drivepool (I think other Pooling software have something similar)

[Carlo 4560]

I do the same thing @rbjtechwith Drivepool on Windows but now run my main system on Linux.  On Linux you can FUSE (overlay) different file systems together which allows you to setup a simple script that runs once an hour moving any file with X extension to the SSD/NVMe.

Combine ZFS pools setup to handle different block sizes and you can customize the file system for different file types including use of compression, ARC caching, special devices that can all be fed from Optane drives which are incredibly fast.

Be it Windows or Linux a bit of creativity can give you lots of options to be creative in your use of disks and organization of your file system while making it appear to be "normal".