AMD StoreMi 2021

Joined
May 11, 2021
Messages
5
I'm very much a novice and ask for your indulgence. I recently built a machine that has 2 500 gb nvme.m2 drives and 2 6 TB HDD.
If I'm putting Plex on the SSD, and files on the HDD, will AMD StoreMi gain me any advantage/performance boost?
 
I'm very much a novice and ask for your indulgence. I recently built a machine that has 2 500 gb nvme.m2 drives and 2 6 TB HDD.
If I'm putting Plex on the SSD, and files on the HDD, will AMD StoreMi gain me any advantage/performance boost?
As in a performance boost for Plex? No. Not at all. It's not limited by I/O speed.
 
Is the only advantage/performance gain, overall, only if I put software on the slower HDD?
StoreMI is in general a form of 'tiered' or 'cached' storage implementation, whereby a SSD accelerates a SSD. So yes, you would put software or data on the HDD and it would be cached by the SSD as a result.

However, nothing StoreMI can do will be faster than simply installing the software on the SSD in the first place. Cache implementations like this are, generally, not what common users will want to implement.
 
StoreMI is in general a form of 'tiered' or 'cached' storage implementation, whereby a SSD accelerates a SSD. So yes, you would put software or data on the HDD and it would be cached by the SSD as a result.

However, nothing StoreMI can do will be faster than simply installing the software on the SSD in the first place. Cache implementations like this are, generally, not what common users will want to implement.
Thanks very much. I was thinking that StoreMi wasn't going to give me any advantage (I had decided against unraid as I would have to learn it).
So, I'm going to put Plex on the SSD along with the metadata (moving Plex from one device to the new one) and the files on the HDD.
Thanks again for being helpful.
 
The new StoreMI is pretty useless. It only caches reads, and does a pretty terrible job at doing that.

I used the old version of StoreMI for a while, which was a tiered-storage solution rather than a caching solution. Then they re-wrote the software to be a fully in-house solution, but changed it to being a simple read-cache only solution.

What's nice about the tiered-storage approach is that you are basically working directly with the SSD (aka the fast tier). Writes are "accelerated" because you're writing directly to the SSD in most cases. New files and files that have been accessed recently stay on the SSD while old files get moved to the HDD. You pretty much get the full SSD experience. Only catch is that if you have a game that you have not accessed in such a long time, that it got automatically moved to the HDD, it will be slower the first time you access it again, after which it will be on the SSD and be fast again. Not a bad compromise really.

I use my StoreMI drive mainly for my VMs, because they simply take up too much space to have the dozen or more VMs that I have all directly on an SSD. With the first version of StoreMI (tiered storage), I can boot 4+ VMs at the same time and it works great. With the new version (simple cache), booting more than 2 VMs at once feels like it's running from a 4200rpm laptop hard drive. The software simply doesn't work very well or really improve much. I ended up switching back to the old version of StoreMI, despite the fact that it's no longer supported. I'm strongly considering moving over to FuzeDrive, a tiered-storage software by the company Enmotus which is what the first version of StoreMI was based on.
 
The new StoreMI is pretty useless. It only caches reads, and does a pretty terrible job at doing that.

I used the old version of StoreMI for a while, which was a tiered-storage solution rather than a caching solution. Then they re-wrote the software to be a fully in-house solution, but changed it to being a simple read-cache only solution.

What's nice about the tiered-storage approach is that you are basically working directly with the SSD (aka the fast tier). Writes are "accelerated" because you're writing directly to the SSD in most cases. New files and files that have been accessed recently stay on the SSD while old files get moved to the HDD. You pretty much get the full SSD experience. Only catch is that if you have a game that you have not accessed in such a long time, that it got automatically moved to the HDD, it will be slower the first time you access it again, after which it will be on the SSD and be fast again. Not a bad compromise really.

I use my StoreMI drive mainly for my VMs, because they simply take up too much space to have the dozen or more VMs that I have all directly on an SSD. With the first version of StoreMI (tiered storage), I can boot 4+ VMs at the same time and it works great. With the new version (simple cache), booting more than 2 VMs at once feels like it's running from a 4200rpm laptop hard drive. The software simply doesn't work very well or really improve much. I ended up switching back to the old version of StoreMI, despite the fact that it's no longer supported. I'm strongly considering moving over to FuzeDrive, a tiered-storage software by the company Enmotus which is what the first version of StoreMI was based on.
Thanks for contribution to my education!
 
Back
Top