TerraMaster Hyper Cache

[Aakriti]

@TMRoy

I guess my expectation was that I would be able to create a hypercache out of a mirrored pair of NVME and carve that pool up amongst more than one volume as I can with other appliances. Not that I can ONLY use the mirrored set for ONLY one volume.

Hi friend
When hardware constraints limit flexibility in pooling and partitioning storage, it is upsetting. Being able to allocate resources as needed can completely alter the situation.

[djacobson]

I know it's 1 SSD per volume. But I just wanted to verify that if I have a 2TB SSD and install it, the largest cache I can create on it is 757GB. (I think.) The rest of the 1.3-1.4TB left is wasted, correct? Better to use a 1TB SSD, yes?

Thanks

[TMzethar]

Your idea is reasonable, as the remaining 1.3-1.4T cannot be used currently after you have create a 757GB cache.

[Gremlin]

Never been quite clear on this, but does the selected cache size determine the amount of system memory consumed by cache? (I don't have a need for cache in my system.) If so, then maybe 500Gb ssd might be more cost effective and set whole of it for cache. (Or a large % to leave some headroom if desired).

[Darsh]

More than one Hyper Cache be created in the system. It seems that only one Hyper Cache can be created and it can be assigned to only one volume which is very limiting. IMO, creating only one volume in a system is always a bad idea.

Agreed! The development of only one Hyper Cache per system and its confinement to a single volume presents issues for system optimization. The option to construct numerous Hyper Caches across different volumes would provide greater flexibility and better cater to a wider range of storage requirements.

[Darsh]

More than one Hyper Cache be created in the system. It seems that only one Hyper Cache can be created and it can be assigned to only one volume which is very limiting. IMO, creating only one volume in a system is always a bad idea.

Agreed, the limitation of creating only one Hyper Cache and assigning it to a single volume can be restrictive. Diversifying volumes in a system is often essential for effective management. Advocating for the flexibility to create multiple Hyper Caches could significantly enhance system customization and optimization.Gb whatsapp Download

[Gremlin]

{L_BUTTON_AT}Darsh

Now you are plagiarizing yourself! Silly.

[CraftyClown]

I know it's 1 SSD per volume. But I just wanted to verify that if I have a 2TB SSD and install it, the largest cache I can create on it is 757GB. (I think.) The rest of the 1.3-1.4TB left is wasted, correct? Better to use a 1TB SSD, yes?

Thanks

I think the cache size is relative to the amount of RAM you have installed. I was only able to use about 300gig on a 1TB SSD when I had 4gig of RAM, however once I added a 16gig stick I was able to use the full amount

[mightymouse]

Need some advice please on Hyper Caching vs using the SSDs as a Storage Pool for my case.

I have 2x 20TB drives at RAID 1 and 2x4TB SSDs available.

On my previous system so far I only used one of the 4 TB SSD to store, download and seed my media library and that was enough space for me though sometimes it gets a little tight. I thought if I add a second SSD and make it 8TB with a Raid 0 that should be plenty and would effectively let me operate a "pure SSD" setup. For data security, I was planning doing a daily rsync backup of the SSD pool to the HDD pool and I am happy to accept the risk of losing 1 day's worth of changes.

Now with Hyper Caching being an option... Does it make sense to continue with my original plan or should I just use one (or both) of the 4TB as a cache instead and "officially" have the media library on the HDD pool? What RAMS requirement do I need for a 4 or 8TB cache?

[TMzethar]

{L_BUTTON_AT}mightymouse

If you want to build RAID0, you can only delete the existing storage pool and use two SSDs to create a new one. Therefore, you need to back up your data first.
If you mainly use SSD as read/write storage, you don't need to use SSD as cache anymore, which does not improve read/write speed. (Because your storage and cache are both SSDs)