279 karma · joined April 14, 2022
* Local time-zones instead of only UTC
* Faster replication jobs
* Enhanced cron job definitions for pull/push jobs
* New configuration for control and prometheus services
The original code works very well, but the new fork has added some enhancements the original author chose not to include.We did an exhaustive test of our use-cases, and the best ZFS tuning options with Postgres we found (again, for our workload):
* Enable ZFS on-disk compression
* Disable ZFS in-memory compression (enabling this option costs us 30% perf penalty)
* Enable primary caching
* Limit read-ahead caching
Edit: Forgot to add, here are the required PGSQL options when using ZFS: * full_page_writes = off
* wal_compression = off
Once the above options were set, we were getting close to EXT4 read/write speeds with the benefit of compression.It does have adaptive cruise control and the ability to stay inside the lines, but it absolutely will not automatically change lanes or exit off the freeway.
I have spent an enormous amount of time over the past couple of weeks tuning ZFS to give us the best balance of reads-vs-writes, but the biggest problem is trying to find the right benchmark tool to properly reflect real-world usage. We are currently using FIO but sheer number of options (depth queue, numjobs, libaio vs io_uring) makes the tool unreliable.
For example, comparing libaio vs io_uring with the same options (numbjobs, etc) makes a HUGE different. In some cases, io_uring gives us double (or more) performance than libaio, however, io_uring can produce numbers that don't make any sense (eg: 105GB/sec reads for a system that maxes out at 72B/sec). That said, we were able to push > 70GB/secs large-block reads (1M) from 12x NVMe drives which seems to validate ZFS can perform well on these servers.
OpenZFS has come a long way from the 0.8 days, and the new O_DIRECT option coming out soon should give us even better performance for the flash arrays.
Based on my own personal experience, good companies want to be accommodating because they understand people truly are the most important resource. They strive for a good balance of company-vs-employee desires. Who knows, maybe I am just lucky; maybe my past 30yrs working for big-tech is an anomaly?
Overall, first impressions are looking good. Found a few bugs that need to get worked out including:
* UEFi boot requires iVentoy to have 2 vCPUs (see forums)
* Restarting the iVentoy script resets the IP Boot config (specifically the Subnet Mask and Gateway)
From their release page, iVentoy supports a bunch of Linux and Windows install images, and you can even inject custom auto-install scripts to the ISO for unattended installs. Very cool. Finally, the iVentoy discussion forum seems very active, and the developer seems engaged.
I will probably support the developer ($49) because he was able to leverage NBD to overcome some iPXE issues I struggled with for a long time. I know how much time/effort goes into making iPXE booting look seamless. Kudos to him/her/them
In my opinion, it's just the "human condition". Like adults, kids want to take the least path of resistance. Since learning is difficult for some/most of us, avoiding school is the easiest path since it requires real effort. This is why parental guidance is so important for young people. Sure, some cities experience violence, some schools have odd teaching mandates, etc, but all-in-all, it's the daily grind that kids want to avoid (just like adults!). Not to mention the pressure from social media.
The others went in the trash as soon as they came in...
I wish my bank had the same sort of option to prevent someone from just randomly guessing my account number for an ACH transfer.