I have two storage nodes and one is much faster than the other.
I’m currently evaluating a juicefs deployment based on two minio instances (one per node, replicated with async bucket replication) through a load balancer (sidekick) in failover. Because juicefs also needs a db for metadata, I went with valkey + sentinel.
Juicefs provides a CSI driver that supports ReadWriteMany volumes and CSI snapshots and manages both read and write cache. Performance is much much better than Ceph. In theory it should be riskier (because of the async replication) but in practice I haven’t yet lost a bit.
Well actually it is very easy to spin up in docker and most of the configuration happens through env variables.
juicefs itself only exists on the client side, so you basically only have to install and configure the CSI driver with helm.
as it took me a few days to come up with this solution I’d be happy to share my config files.
Performance wise is quite fast on sequential reads (it saturates my 2.5G bandwidth) and slower than I expected on sequential writes (for me it caps at 60MB/s). Postgresql seems happy. I saw no visible performance degradation with Authentic, Immich and Opencloud. Nextcloud installation took ages. I’ve yet to try it with jellyfish and the *arr suite.
A simple NFS share would be faster, but it doesn’t support replication, failover and CSI snapshots.