react-native-mmkv-storage VS autotier

As title says, is it a good option? There'll be like 60 webp images not some high quality. Or should I add some local db instead, something like: 1. https://github.com/ammarahm-ed/react-native-mmkv-storage 2. https://github.com/Nozbe/WatermelonDB

Use mmkv storage to make it faster

watermelondb https://github.com/Nozbe/WatermelonDB mmkv giving another issue when you release on playstore in here https://github.com/ammarahm-ed/react-native-mmkv-storage/issues/194

roll your own with asyncstorage (or RN mmkv https://github.com/ammarahm-ed/react-native-mmkv-storage ) and react query

Async Storage is slow/limited though, the new black is MMKV - https://github.com/mrousavy/react-native-mmkv or https://github.com/ammarahm-ed/react-native-mmkv-storage

If you use Async Storage in your React Native App, you should give react-native-mmkv-storage a try. The fastest storage library for react native built with JSI.

It's been a year now and with the extensive support from community, react-native-mmkv-storage has gotten even faster than it was using JSI. I have rewritten the whole library in C++. There are no `@ReactMethods` or the old bridge anymore. Everything happens in C++ which makes this library the fastest solution available for your apps.

In my experience cookies does not play well with RN. In my apps I usually receive the token on the authorization header of the sign in/sign up response. I store it (I use react-native-mmkv since it provides encryption and compatibility with redux-persist out of the box) and append it to every request (using Axios). When the user logs out and for 401 responses I clean the storage

maybe tiered storage for HDD pool (if I find a good solution - I was thinking about 45drives autotier but not much info about it)

If using LVM isn't an option for something like this I did find autotier which appears to implement everything I need under a FUSE but I'm concerned about the performance overhead of that. Since the entire point of storage tiering would be improving performance would a FUSE system be practical?

My workload is primarily Plex media server, NFS/SMB. Going to UNRAID for everything could work; but I could also do a unraid hybrid setup with 2 disks ZFS mirror for my documents and photos while leaving the movies+tv files in other disks (this would increase my hdd count from 4 to 5 though due to parity needs)... a third option (probably very time consuming) is openmediavault + https://github.com/45Drives/autotier + ZFS (on each disk, simply to get the ability to 'zfs send/receive' to backup to another zfs server nightly)

I just installed unraid to test and see if I should be moving all my files to it from ZFS for my home media server (movies, tv, large backups, etc). I think the feature I want to exploit the most of unraid is the possibility to use a nvme-cache drive then purge data to disks after XX days or so - this basically feels like https://github.com/45Drives/autotier in a way.

Is anyone using Autotier (https://github.com/45Drives/autotier) or similar on NixOS? How did you set it up?

Given current pricing, larger SSDs, in terms of about 1TB aren't actually twice the price of 512GB ones, which in turn aren't twice as expensive as the 256GB units, seem to be better buys. At the same time, there are benefits to going SSDs for certain capacities and workloads, while in many cases a correctly functioning tiering system is more beneficial. Qnap's Qtier, however, is using dm-thin/md-adm features that are not in use/available by design in QuTS Hero and as such their regular QTS's feature of Qtier is unavailable on the ZFS-based variant. SSDs can be used for SSD pools or caches (as in ZIL for writes/L2ARC for reads/metadata for metadata and deduplication tables or a mix of those) only, similar to QES. Contrary to QES target audience, many ZFS-powered units are reaching customer base that is more home, SOHO or even light on the budget, so going with "huge" (in terms of disk quantity and overall capacity) and resilient all-flash pools is merely a dream, so the caches are more or less the goto option. As stated earlier, this leads to often either overexpenditure or underutilisation of the disk resources. Still, Qnap seems to have been quite tight-lipped about any possibility of Qtier-like solution being offered in their QuTSHero stack for a long time (presumably either because they don't want to offer it to not canibalise any of the remaining comparative QTS only or QES solution sales, or due to their inablity to come up with a solution). Given that the underlying system is a tuned linux, I wonder why autotier-like (https://github.com/45Drives/autotier) FUSE filesystem has not been prepared as a "replacement"/alternative. Sure, block-level monitoring/tiering would have been even better but the nature of COW/ZFS does not play well with regular block-monitoring tools (one could splice something up but that would require yet another huge table for block counts tracking to combine spinning rust and silicon traps in persistent and ephemeral levels into one global map for storage). However, a FUSE filesystem of autotier deals in file-level analysis, which would greatly increase usefulness of a mixed SSD and HDD pools appliance possibly without incurring much of a performance impact. Qnap certainly has the manpower or funds to prepare a solution that is unique/optimised for their devices that while not as good at moving hot data around as the block-level solution, would be the next best thing without too much of a hustle and it could still joggle around data when required. The question then remains, why haven't Qnap gone through with releasing such a solution, or maybe there is one in the works that Qnap plans to add as a showcase for QuTS Hero v.5? It could greatly improve the QuTS perspective in devices such as TS-673A (wherein one could than get a 3-tier solution with 2x NVMe SSDs for hottest files/data or caches, and the 6 drivebays populated with 3x HDDs for cold and 3x SATA SSDs for warm data layers) or its 8-bay counterpart, or the TS-h973AX (wherein we're getting 3 tiers by design with 2x U.2 for hot sauce or caches + 2x SATA SSDs for warm data + 5x HDDs for cold storage) as example units of somewhat lower pricing in the ZFS-based range/spectrum. This could certainly boost sales of the ZFS units. Or maybe, I've just been deaf and blind to the corporate PR to that degree that I've missed Qnap official unveiling of a future showcase piece plans for later? Or maybe such features have crept silently in some beta releases already and been dropped due to some issues?

I also found autotier, which implements a sort-of storage tiering solution on top of ZFS.