DragonflyBSD 5.0
This is a big release for a few reasons:<p>* major new filesystem (Hammer2)[1]<p>* OpenBSD might even adopt Hammer2 has a replacement of it's legacy filesystem [2]<p>* huge work on network performance. DragonflyBSD is agrubably the fastest BSD for network intensive tasks [3]<p>* IPFW has been rewritten to be multi-threaded which has resulted in huge performance improvements [4]<p>[1] <a href="https://gitweb.dragonflybsd.org/dragonfly.git/blob_plain/HEAD:/sys/vfs/hammer2/DESIGN" rel="nofollow">https://gitweb.dragonflybsd.org/dragonfly.git/blob_plain/HEA...</a><p>[2] <a href="https://marc.info/?l=openbsd-tech&m=142755452428573" rel="nofollow">https://marc.info/?l=openbsd-tech&m=142755452428573</a><p>[3] <a href="https://leaf.dragonflybsd.org/~sephe/perf_cmp.pdf" rel="nofollow">https://leaf.dragonflybsd.org/~sephe/perf_cmp.pdf</a><p>[4] <a href="http://lists.dragonflybsd.org/pipermail/commits/2017-September/626329.html" rel="nofollow">http://lists.dragonflybsd.org/pipermail/commits/2017-Septemb...</a><p>UPDATE:<p>To also give context as to what Dragonfly BSD is, DragonFly BSD was forked from FreeBSD 4.8 in June of 2003, by Matthew Dillon over a differing of opinion on how to handle SMP support in FreeBSD. Dragonfly is generally consider as having a much simpler (and cleaning) implementation of SMP which has allowed the core team to more easily maintain SMP support; yet without sacrificing performance (numerous benchmarks demonstrate that Dragonfly is even more performant than FreeBSD [5]).<p>The core team of Dragonfly developers is small but extremely talented (e.g. they have frequently found hardware bugs in Intel/AMD that no one else has found in the Linux/BSD community [6]). They strive for correctness of code, ease of maintainability (e.g. only support x86 architecture, design decisions, etc.) and performance as project goals.<p>If you haven't already looked at Dragonfly, I highly recommend you to do so.<p>[5] <a href="https://www.dragonflybsd.org/performance/" rel="nofollow">https://www.dragonflybsd.org/performance/</a><p>[6] <a href="http://www.zdnet.com/article/amd-owns-up-to-cpu-bug/" rel="nofollow">http://www.zdnet.com/article/amd-owns-up-to-cpu-bug/</a>