Minimum requirement for ISCI

HI! I host proxmox on 7945Hx 16c 32th 94Gb machine, hosting TrueNas scale and 10GB connecting network.

Can i run ISCI (to use with my kubernets Cluster)? how many CPU and MEM i have to allocate?
Thanks

1 Like

CPU and memory overhead should be relatively small.

The biggest concern are synchronous writes. Is your system using an SSD pool or does it have a SLOG?

I don’t know about cores, but a minimum of 64 GB RAM is recommended for iSCSI—and preferably more.

actually i don’t have any additional special VDEV only 32G of memory

Thanks for your answer.
Even for an Homelab too? I want only an faster alternative to NFS in my 10Gb Kubernetes 3 node Cluster, so is important to be faster then NFS but absolutely no enterprise performance.

…and what makes you think iSCSI will be faster than NFS?

1 Like

Because googling/chatgpting I found it, obviosly I will use iscsi only for one node, i will leave shared use on NFS.

Yes. iSCSI handles more metadata than NFS/SMB.

I know nothing faster than NFS for Unix/Linux nodes. You may need to dive into:

  • checking and optimising networking (iperf3);
  • disabling sync writes on NFS, if that is acceptable;
  • or adding an Optane SLOG.

How to? and what implies disable sync writes?

Thanks
Olindo

Please don’t do this.

iSCSI is, above all else, different than NFS as a block-level rather than file-level protocol. Even if you elect to utilize it in some capacity…there’s just so much that’s fundamentally different. You should research what iSCSI is and how you would architect it in your situation before worrying about something as fuzzy as “minimum requirments” (which you…don’t really want)

are you currently using sync writes and how do you feel about data loss?

Set sync > disabled in dataset properties. The consequence is that the client has no confirmation that writes have been committed. If the shares host apps/VMs, there’s a risk that an unexpected shutdown could corrupt the installations.

1 Like