A running description of activity related to DragonFly BSD.
I have some pkgsrc-2011Q3 builds done, for x86_64 and i386. I performed them on DragonFly 2.11, but they should work fine for 2.12/2.13. They’re uploading to the pkgsrc-2011Q3 folder on mirror-master, so you’ll need to set PKG_PATH correctly to use them via pkg_radd.
PKG_PATH=http://mirror-master.dragonflybsd.org/packages/x86_64/DragonFly-2.13/stable/
The x86_64 package upload is done, and I anticipate the i386 one will be done within the next 24 hours.
I did not realize this, but MMC/SD cards are not supported in the default DragonFly kernel. Or at least, they weren’t until now. (also committed to 2.12)
Update: PCI-based MMC/SD readers, specifically. USB ones were already recognized as umass devices.
They aren’t really release candidates per se, just “images I built from the 2.12 branch”, but they are available for testing.
There’s only two commits, already in DragonFly-current, to add to 2.12 before it’s clear of all listed release requirements. And maybe binary package builds… which I’m about 2/3 of the way through.
It looks like Sepherosa Ziehau is working on hardware support being split up per-CPU, judging by this commit – one of many, recently.
Tim Bisson’s work on TRIM support has been committed. I don’t know if it will show in 2.12, but it’s off by default so it would seem a safe move.
There’s only one multiprocessing bottleneck left in DragonFly: vm_token. Matthew Dillon’s working on removing it, and he’s been testing his initial results on a 4-core machine and a 48-core machine, using heavily parallelized buildworlds to test concurrency. He’s posted the results, showing an initial speedup of up to 30%. This definitely isn’t going to make it into 2.12, but it’s looking good already. Keep in mind these are improvements on top of the performance graphed here yesterday.
Venkatesh Srinivas sent along a graph of his nmalloc testing that shows mysql threading performance on DragonFly, from slightly over a year ago. Both graphs were done on a 4-core system, though I don’t know if the specs are comparable, so the curve is important. Look at the just-posted curve for comparison. That’s how much things have improved.
In fact, here’s a cheesy overlay, cropping the more recent results and laying the old ones on top of it. The black lines are the year-ago performance, and the colored lines are the performance now.
Samuel Greear has graphed out the performance of both MySQL and Postgres on DragonFly 2.12 as you add threads. There’s a very nice correlation on performance and number of cores. For comparison, there’s this old test from 2007 which shows uniprocessor performance to be good but not improved by adding cores. The tests were on completely different hardware, so the actual curve of the graph is the telling point.
As he points out in his post, excellent multiprocessor performance is arriving on DragonFly, without any catastrophic shifts or destabilizing changes.
The 2.12 branching generated a list of every DragonFly commit since 2.10, grouped by committer. Good to browse through. Try to ignore the part where it shows the measly 4 things I did, with poorly constructed commit messages.
It’s not the 2.12 release yet – just the initial branch of 2.12. This will become the release version of 2.12 in a few weeks.
Did you notice zgrep went missing? Well, it’s available again, thanks to YONETANI Tomokazu.
Michael W. Lucas is setting up two DragonFly machines, to try out Hammer. I linked to his tweet about this in the last Lazy Reading post, but this is a more in-depth explanation of what he’s doing. So far, it just works. (as seen on Reddit, too.)
I finished a build of pkgsrc-current on x86_64, with a report on what built. I’ve kicked off a new build, and I expect at least 100 more packages to build thanks to John Marino’s work on pkgsrc and DragonFly.
Want to create getcontext for DragonFly/x86_64? Apparently we need it.
This week’s Lazy Reading just built itself up quickly; autumn arrives in the northern hemisphere and suddenly a lot more activity starts going on.
There are four ways to deal with system damage: 1) reliability, 2) redundancy, 3) repair, and 4) replacement.
I’ve put together a catch-all ticket for remaining issues to fix before the 2.12 release of DragonFly: Issue 2135. Several of the issues have already been dealt with by Peter Avalos and Sepherosa Ziehau, so a hat tip for them!
Peter Avalos has updated OpenSSH to version 5.9p1. This might be the last thing before the next DragonFly release.
Update on the update: he updated OpenSSL (1.0.0e) and file (5.09) too.
Francois Tigeot has done another set of benchmarks using blogbench to test reading and writing under different DragonFly versions, plus some OpenIndiana benchmarks just to mix it up. Writing performance seems to have drastically improved between DragonFly 2.10 and 2.11.
His post has an attached PDF with, of course, graphs. This site has previously mentioned other not-really-comparable disk testing performed by Francois.
