I installed a DB-Server for a Customer around 2years ago, in a DC near him with 16 cores 48GB Ram and ~6TB -> 12 SSD, vDevs mirror with 2, and zRaid0 over the mirrored vDevs (kind of a Raid10), compression zstd (1GB could be compressed down to ~200MB so 5 times less reading/writing, and in theory ~30TB of pure DB-Data, 20TB realistic, remember never fill a zpool over 72%) and record-size 16kb. After 3 month the machine was paid (compared to the "cloud"-price) and the performance kind of 10-12 times higher.
Called the customer about a two month ago and he said the DB-Server is still to fast and maybe he wants another one who uses less power... ;)
Could you please explain where this number comes from?
>Yeah, that's a myth now. It's not current advice.
It's not and you know it, keep it under 72% believe me if you want a performant zfs (especially if you delete files and have many snapshots...check the YT linked at the end)
>>Keep pool space under 80% utilization to maintain pool performance. Currently, pool performance can degrade when a pool is very full and file systems are updated frequently, such as on a busy mail server. Full pools might cause a performance penalty, but no other issues. If the primary workload is immutable files (write once, never remove), then you can keep a pool in the 95-96% utilization range. Keep in mind that even with mostly static content in the 95-96% range, write, read, and resilvering performance might suffer.
https://web.archive.org/web/20150905142644/http://www.solari...
And under no circumstances go over 90%:
https://openzfs.github.io/openzfs-docs/Performance%20and%20T...
>An introduction to the implementation of ZFS - Kirk McKusick
PostgreSQL is pretty much parallel but i know what you mean...the beehive ;)
Over last ~6 years we did "is it worth going to cloud" calculation few times and it was always ridiculously more expensive.
We pay 7k per month for RDS that can do barely 2k iops.. in the same time a machine at hetzner does 2 million iops for 250 euro per month (not to mention it also have 4x more codes and 5x more ram).
So, even though I/O is no longer the bottle neck physically, it still is a considerable issue and design challenge on the cloud.