Samuel Greear, Jan Lentfer, and others are looking at Postgres scaling on DragonFly. The work they are doing isn’t in the tree yet, but here’s a graph showing some of the performance differences.
Francois Tigeot does something very useful: he monitors the resource usage on his systems, and tracks how it changes over time. Because of that, he noticed that the recent VM changes in DragonFly have made quite a difference in memory usage. (See the green area in the attached chart, around week 42.)
Michael Lucas is building jails on DragonFly, and his story of doing so works pretty well as a how-to guide.
DragonFly’s now on the BuildFarm list of Postgres test systems. (via Jan Lentfer in IRC)
Did you know that there’s a BSDDay 2011 in Bratislava, Slovakia, on November 5th? Well, I do thanks to a random Google search and now you do too. You and I both need to keep watching BSD Events.
Samuel Greear graphed the performance differences for Postgres and MySQL on DragonFly, before and after the recent VM changes. Note that 1: this was done a little while ago, so I think the performance difference would be even greater now, and 2: this was graphed versus the already-performing-better 2.12, not the current stable release of 2.10.
Google’s running the Code-In project again for 2011, where open source projects mentor 13-17-year-olds on a variety of small projects. DragonFly participated last year and had lots of good work done. However, we need ideas, the more the better. Please add whatever comes to mind.
There’s a rare crash in DragonFly 2.10, where applications would segfault. The system would run find. This is apparently more likely to happen in 2.12, though reports on this vary. It’s real, though.
Matthew Dillon went looking for this bug, and happened to roll back vm_token, the last lock in DragonFly that presented a serious impediment to multiprocessing. It’s a big patch. It fixes the problem, which is great! It also happens to make DragonFly buildworlds almost twice as fast depending on the number of cores in the system.
Holy crap we want to get that out… but it makes some significant changes to the system and needs to be tested. So, the next release probably won’t be for a few weeks.
If you want to help, build master and do something with it – move data, run server programs, whatever. Report crashes. This performance improvement is worth working for.
I didn’t know this existed, but there it is: the BSD Router Project is a software router, which just reached version 1.0. (via)
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.
Dennis Ritchie, one of the people behind UNIX and the C language, has died. (via skullY on #dragonflybsd on EFNet) Look at his Bell Labs web page for some details on his history. The death of Steve Jobs will get a lot of media attention, but I’d argue that Ritchie affected more computers in far more ways.
Among other changes to pkgin 0.5 (available in pkgsrc-wip but not pkgsrc-2011Q3), it now notices if you need a newer pkg_install because you’ve shifted to a more recent quarterly release of pkgsrc, and grabs the appropriate binary package to fix that. Thanks, iMil!
User ‘Zenny’ asked questions about setting up a server similar to ones described in this presentation, except using DragonFly and Hammer. Most of it is possible now, going by the thread.
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.
The Open Source Business Resource, linked here before, has become the Technology Innovation Management Review, or TIM Review. Conveniently, the editor is named Chris, not Tim, so nobody will get confused. It’ll still cover open-source software, but it’ll also
“share the spotlight with topics such as managing innovation, technology entrepreneurship, and economic development”
The first relaunched issue will be out in October.