Earlier quoted context omitted.
I run a little VPS on DragonFlyBSD that I use for misc hobby projects and personal file hosting. Mostly it runs Postgres. It's quite fast. I had redis running on there as a message queue for a distributed web crawler for a while. I benchmarked it against Arch Linux (which is what I was using on that server before DragonFly) and it was somewhat faster. HAMMER is a really nice filesystem. It's not one of the fancy COW…
What benchmarks showed an improvement between Arch and DragonFlyBSD?
DragonFly BSD 4.8 released
21–30 of 35 posts
Re: DragonFly BSD 4.8 released
#22Earlier quoted context omitted.
I know you probably meant "gold standard" but I was amused thinking about what a golf standard might mean ;)
Why do you assume he meant "gold standard"? Have you ever seen how fast a golf ball flies just after a strong hit?
Re: DragonFly BSD 4.8 released
#23In 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 Fr…
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.
Re: DragonFly BSD 4.8 released
#24Earlier quoted context omitted.
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.
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…
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.
Re: DragonFly BSD 4.8 released
#25Earlier 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…
Re: DragonFly BSD 4.8 released
#26In 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 Fr…
> 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.
Re: DragonFly BSD 4.8 released
#27In 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 Fr…
I know you probably meant "gold standard" but I was amused thinking about what a golf standard might mean ;)
Re: DragonFly BSD 4.8 released
#28Earlier 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…
Without CRCs or checksums on the blocks. Grr...
"Silent data corruption is real" https://news.ycombinator.com/item?id=13851349
Re: DragonFly BSD 4.8 released
#29Re: DragonFly BSD 4.8 released
#30Earlier quoted context omitted.
I know you probably meant "gold standard" but I was amused thinking about what a golf standard might mean ;)
I just assumed "golf standard" was some QA term I hadn't heard of before.
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.