Bulk build results for 2011Q3

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.


The x86_64 package upload is done, and I anticipate the i386 one will be done within the next 24 hours.

GEM/KMS warning

Some newer laptops have Intel integrated video chipsets that require GEM/KMS to work well; they are supported by the vesa driver in X, but performance isn’t great.   Johannes Hofmann found this out the hard way.  GEM/KMS support is on the way for various BSDs, but it’s not here yet.  Just be aware of this if shopping for a new laptop in the next little while…

Lazy Reading for 2011/10/09

Getting close to 2.12 release…

The last MP step

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.

More performance graphing

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.

Improved DragonFly threading performance

Performance curve for DragonFly 2.12

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.