[tiffanyh]

In case people are wondering what makes DBSD so interesting, DragonflyBSD is:

- focused only on x64 architecture

- has an extremely small but exceptionally talented team of developers (e.g. Matt Dillon from DICE and Amiga fame)

- has it's own unique filesystem called Hammer (and work is being down on Hammer2 which is a complete rewrite)

- Network performance is particularly good with Dragonfly and even better than FreeBSD which is known as being the golf standard for network performance [1]

[1] https://leaf.dragonflybsd.org/~sephe/perf_cmp.pdf

Edit: formatting

Edit2: it should also be noted in the release notes, it refers to detailed NVME disk performance testing the Dragonfly team performed. These results are largely agnostic of what OS you run. Really interesting to see the Samsung NVME device come out on top and Intel in last. This is a good read even if you don't run Dragonfly.

http://apollo.backplane.com/DFlyMisc/nvme_randread.txt

[eternalban]

> - 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 efficiently on small storage systems.  The
     minimum recommended file system size is 50GB.  HAMMER must reserve 512MB
     to 1GB of its storage for reblocking and UNDO/REDO FIFO.  In addition,
     HAMMER file systems operating normally, with full history retention and
     daily snapshots, do not immediately reclaim space when files are deleted.
     A regular system maintenance job runs once a day by periodic(8) to handle
     reclamation.

     HAMMER works best when the machine's normal workload would not otherwise
     fill the file system up in the course of 60 days of operation.  

And what appears to be the original design doc for Hammer by Dillon: https://www.dragonflybsd.org/hammer/hammer.pdf

[& p.s.] Hammer2: http://gitweb.dragonflybsd.org/dragonfly.git/blob/b93cc2e081...

[tiffanyh]

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 created 30-40 years ago.

So don't view a rewrite as a bad thing. It's Dragonfly being proactive and keeping up with the times.

[adekok]

> Apple themselves just today released an entirely new file systems that was a complete rewrite as well.

Without CRCs or checksums on the blocks. Grr...

"Silent data corruption is real" https://news.ycombinator.com/item?id=13851349

[JdeBP]

> 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.

[h1d]

Only history proves stability.

[cat199]

Hammer1 is a log-structured snapshottable data filesystem with near-live master:slave replication, similar to e.g. zfs/btrfs, with very low memory requirements.

Hammer2 will, last I checked, enable multi-master clustered volumes plus replicated fanout mirrors and caching clients at the base system level (e.g. not an overlay application like other systems)

While there is a focus on keeping releases as stable as possible and the tip of the source tree stable, it is heavily under development so some amount of low-level expertise is probably a good idea.. which isn't to say you can't use it for day-to-day use.

Systems are used for different things - one being heavily under development doesn't necessarily mean it isn't suitable for some use cases

[AtticusTheGreat]

I know you probably meant "gold standard" but I was amused thinking about what a golf standard might mean ;)

[djsumdog]

I just assumed "golf standard" was some QA term I hadn't heard of before.

[nickpsecurity]

It could be part of MIL-SPEC evaluation. They'd be concerned with how many times you could hit the evaluated product with a golf club before its effectiveness degraded. Also how many times before it stopped working. These numbers would provide actionable intelligence to acquisitions officers in the military on how to order just enough replacements for given scenarios while minimizing the amount of unnecessary orders.

Long story short, applying the golf standard in your QA process can both increase longevity of the product and reduce replacement costs. Many government organizations and enterprises running mission-critical applications might find DragonflyBSD servers attractive if they passed the golf standard. They could combine it with their Five 9's middleware.

[akerro]

Why do you assume he meant "gold standard"? Have you ever seen how fast a golf ball flies just after a strong hit?

[flukus]

Never from the point of view I'd like to see it from.

[fnj]

HAMMER2 has been worked on for at least 6 years; AFAICT by one guy. Every year it is supposed to be happening Real Soon Now, but never appears to make any evident progress.

Matt Dillon does very impressive work, but the critical mass just isn't there.

[mjn]

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 CephFS is production-ready (and still many don't trust it).

[cyberpunk]

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 several clients) and there are no features I need in ceph which would make me take the less mature option.

I've been using LeoFS a little lately also again ontop of ZFS and it's working reasonably well (S3 compat stuff).

Currently why anyone would use HAMMER2 or BTRFS for anything important escapes me.

[JdeBP]

You might enjoy the discussions at https://news.ycombinator.com/item?id=13929692 .

[mozumder]

> Really interesting to see the Samsung NVME device come out on top and Intel in last. This is a good read even if you don't run Dragonfly.

The Intel device tested was their absolute lowest end consumer part. The 750 and above drives are completely different beasts, especially at the server level.

[loeg]

The 750 series also costs a lot more, while the 600p is comparable in price to Samsung's 960 EVO. The numbers are still interesting :-).