Earlier quoted context omitted.
What benchmarks showed an improvement between Arch and DragonFlyBSD?
redis's redis-benchmark utility. Sorry if that wasn't clear.
If you have a copy of the results, that will be awesome ! Thanks !
DragonFly BSD 4.8 released
31–35 of 35 posts
Re: DragonFly BSD 4.8 released
#32I appreciate that there is so much operating system innovation coming from the *BSD's like the Hammer file systems in DragonFly and security concepts like the new pledge() system call from OpenBSD which informs the operating system that an executing program pledges to never use certain system calls. (i.e. if you say you'll never do something, the operating system will have the privilege of killing your application sh…
Re: pledge() in OpenBSD:
In FreeBSD for quite some time there is Capsicum and CloudABI has been included in FreeBSD 11. Definitely worth a look, especially the second which is also present in DragonFly.
Re: DragonFly BSD 4.8 released
#33Earlier quoted context omitted.
> - has it's own unique filesystem called Hammer (and work is being down on Hammer2 which is a complete rewrite) You said "interesting", but superficially "a complete rewrite" WIP doesn't sound like a plus when choosing a production system OS. If anyone is interested, this is what the DBSD man page says about hammer: HAMMER file systems are designed for large storage systems, up to 1 Exabyte, and will not operate eff…
In all fairness to Dragonfly, Apple themselves just today released an entirely new file systems that was a complete rewrite as well. With the advent of SSD and NVME, how you achieve maximum performance and ensure long term "disk" endurance has radically changed in recent years. You're no long write data to a physical platter anymore. Which radically changes huge fundamental assumptions in how legacy file systems were…
> Which radically changes huge fundamental assumptions in how legacy file systems were created 30-40 years ago.
Actually, it doesn't. It makes the ones that you haven't heard of interesting again. Consider the BSD 4.4 LFS, for example. The disc is written to as a circular log, with all writes going to the head of the log, which gradually works its way across the whole disc, and a cleanup mechanism emptying the tail of the log. That is global wear levelling in the file system ... in a design from 1990.
This is what you miss when you adopt the mindset that mis-uses the word "legacy" like that.
Re: DragonFly BSD 4.8 released
#34Earlier quoted context omitted.
It's possibly too big a task for one person, I agree. If he manages to get something usable in even 10-15 years, though, I'd be impressed. HAMMER2 is a clustering file system with POSIX semantics, and by the standards of that category, I don't think it's going all that slowly, to be honest. Ceph has had probably hundreds of person-years of development put into it, and only very recently have people started claiming C…
In $dayjob, I'd still go for gluster over ceph, with zfs on my storage nodes -- this obviously depends on what you're doing but in my case this would be shared storage for everything from images, logs and dataflow between some chunky legacy apps. Why this stack? For no other reason really other than it works perfectly, has caused me almost no pain in the 6+ years I've used it for this kind of DFS stuff (across severa…
You might enjoy the discussions at https://news.ycombinator.com/item?id=13929692 .
Re: DragonFly BSD 4.8 released
#35Checking the release notes, it does include the recent fix mentioned at https://news.ycombinator.com/item?id=13882171 .