NVME Caching anyone?

[hradec]

I'm implementing a secondary caching mechanism that sits in between the frame reading/decoding and the ram cache.

Essentially, the idea is to write frames to a scratch path (a nvme fast local disk) as they are fed to the ram cache, to create a fast local retrieval disk cache (much larger than RAM) to improve the responsiveness when playing .mov media files that use HEVC encoding directly, without having to extract de .mov to individual frame files.

RV will keep decoding the video frames as long as the nvme scratch path size limit allows (the same as RAM cache does), but in this case it can be way bigger than the available RAM for caching (whatever amount of TB you have on the NVME).

That way the RAM cache will be fed from the NVME frames directly if they are available, achieving realtime playback and scratching of large HEVC .mov files with minimum effort.

Off course it works with any file types, so it may be useful to improve playback of .exr/.dpx/.png files that reside on 1Gbit NFS/SMB storages, specially for files with multiple AOV channels.

Also, it can be enable or disabled(default) so people can choose if they want to use it or not.

Is this something of interest of someone here in the community? If so, I can make it tidy to submit as a pull request.

Cheers...
-H