Best dataset-layout for apps between SSD and HDD pools (Plex and Immich)

Apps and Virtualization
1

Hello

So im setting up Plex and Immich on TrueNAS for the first time, and would like to check with more experienced people if im going a good or bad route.
I have one SSD-pool and one HDD-pool. Im using SSD-pool for apps-install in TrueNAS.
But to ensure best performance for apps running, I would have most of the data on HDD-pool as there is “limited” space on SSD-pool.

Plex
So for Plex, I have tried to figure out what might use lots of space, and what wont.
Is the following a good layout considering speed/storage-usage for the Plex-app?

Plex
Plex1150×808 71.5 KB

Immich
When it comes to Immich, for now i have around 100GB of photos that will be added to the app. However, i will need to plan ahead for up to 1TB of photos and videos (when/if i get family-members onboard).
Its my first time using Immich, so i have lots to learn here before “going live”…
For Immich, i havent created any datasets yet, but would something like this be good?
SSD: thumbs, profile
HDD: library , pgBackup , pgData , uploads , and video

System

System OS:
TrueNAS Scale 24.10.2

System
SuperMicro X10DRI-T4+
2x Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
256GB ECC RAM

HBA IT-mode
1x LSI 9300-16i
1x HP220/LSI 9205-8i

Cabinet:
InterTech 4U-4424
6 rows of 4-wide drive-slots
Each row has its own SAS/SATA backplane, one SAS-cable to each row from the HBA’s.

PSU:
Corsair HX1000i 1000Watt

Pools

Boot
Mirror:
2x 480GB HPE MK000480GWUGF SSD

Storage:
SSD_Pool
1 x RAIDZ2 | 6 wide | 894.25 GiB
6x 960GB HPE-branded MK000960GWSSD

BygdePool
3 x RAIDZ2 | 6 wide | 12.73 TiB
12x 14TB drives HPE-branded MB014000GWUDA
6x 14TB drives Seagate ST14000NM001G

Thanks for any help and suggestions

2

Plex :

Put app on SSD
Videos go to HDD

Immich :
DB goes to SSD
Photos go to HDD

Keep in mind, you don’t want to spin HDDs for no reason just because Plex wants to write to log file.

There is absolutely nothing special in Immich. Its pretty much Postgres DB with metadata + thumbnail cache and your original photos.

You build the database once and after that its simple rescans to pick up changes.

3

i got a question on this: i am in the process of selecting new storage media for a new SCALE build, does it make sense to go SSD all the way or would HDD suffice? I did the setup with 2 small 120Gb SSD’s i had in my stash just for testing but now i want to get real to prepare migrating from CORE to SCALE. Fact is that a 5Tb 2.5" HDD is half the price of a 4Tb SSD. I am not sure it is worth the difference.

4

That 5TB 2.5" HDD is also guaranteed to be SMR, and therefore not recommended for (or really suited at all for) ZFS. :wink:

1 Like
5

His main system says 4 x HGST 2TB SAS in Raid-Z1, so maybe the 2.5 is a SAS drive?

6

SAS tapped out even smaller, 2.4TB if I recall correctly - although that one is not SMR.

7

This is for a new 1U server build, not my current one. I have one internal SSD which is my boot drive with SCALE installation and 2 x 2,5" hot-swap bays. The 5TB 2.5" HDD is a Seagate Barracuda. It doesn’t mention anything in the specs about SMR. The SSD’s are 4TB WD RED SA500 or Samsung EVO 870 4TB. I am not looking for more storage space as i have 5 TB in my current rig and still lots of space left.

8

Datasheet is showing SMR, if I have the correct one.

1 Like
9

so it seems. In the mean time i decided on the 4TB SSD’s. Now i just need to figure out if i go Samsung EVO 870 or WD AS500