kbench
piraeus-operator
Our great sponsors
| kbench | piraeus-operator | |
|---|---|---|
| 2 | 6 | |
| 129 | 345 | |
| 7.0% | 4.6% | |
| 2.6 | 9.0 | |
| 20 days ago | 3 days ago | |
| Shell | Go | |
| Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kbench
-
Longhorn alternatives
From your post history, it looks like you're using RPis, in which case the intrinsic latency of the USB controller is starting you off on the wrong foot. etcd doesn't like latency > 10ms. Have you tested your setup with kbench or something similar?
-
[Recommendation request] 3 servers that need 10GB/s (4 ports preferred, 6 max)
I've bene following their issues about HDD and they say HDD is not recommended but is not a no-go. They state that HDD works up to a certain load, and they are looking to improve it. I believe this benchmark tool by Longhorn does 4K random writes... https://github.com/yasker/kbench
piraeus-operator
-
Has anyone tried TrueNAS Scale and DRBD, Pacemaker Corosync etc
https://piraeus.io/ might be a good option rather than longhorn, check it out.
-
Longhorn alternatives
Linstor using https://piraeus.io/
-
Distributed Storage in a WAN Setting
For kubernetes I also tried https://piraeus.io/ which is a drbd-operator for kubernetes; it creates+mirrors LVM volumes between nodes. In my experience it was faster than ceph although not 100% stable; sometimes a volume would get stuck on a node and only a reboot could help.
-
Which block storage solution to self host ?
Take a look at https://github.com/piraeusdatastore/piraeus-operator
- Openebs ?? Or equivalent
-
Comparing Ceph, Linstor, Mayastor and Vitastor Storage Performance in Kubernetes
A lot better.
A couple of years ago I could see volumes on Linstor getting completely stuck and unrecoverable whenever the network was getting busy or unstable. Nodes reboot were a nightmare too.
Have a setup now with their Piraeus operator[1], Kubernetes >= 1.20, rancher and calico, and it seems to be very stable. XFS have been giving better results too. Still, better not to try too many reboot loops on the nodes.
1: https://github.com/piraeusdatastore/piraeus-operator/
What are some alternatives?
dbench - Benchmark Kubernetes persistent disk volumes with fio: Read/write IOPS, bandwidth MB/s and latency
rook - Storage Orchestration for Kubernetes
kubernetes-k8s - 🖊️ Some notes about Kubernetes (k8s), Docker, Storage.
linstor-server - High Performance Software-Defined Block Storage for container, cloud and virtualisation. Fully integrated with Docker, Kubernetes, Openstack, Proxmox etc.
longhorn - Cloud-Native distributed storage built on and for Kubernetes
lvm-localpv - Dynamically provision Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes that is integrated with a backend LVM2 data storage stack.
grpc_bench - Various gRPC benchmarks
kubegres - Kubegres is a Kubernetes operator allowing to deploy one or many clusters of PostgreSql instances and manage databases replication, failover and backup.
gluster-kubernetes - GlusterFS Native Storage Service for Kubernetes
zfs-localpv - Dynamically provision Stateful Persistent Node-Local Volumes & Filesystems for Kubernetes that is integrated with a backend ZFS data storage stack.
service-mesh-benchmark
kube-linstor - Containerized LINSTOR SDS for Kubernetes, ready for production use.