Posted on
Holy crap, look at those numbers

Remember the new scheduler work?  Well, it continued, and now Francois Tigeot has posted pgbench benchmarks of the progress and benchmarks of DragonFly vs. other operating systems.  The links are to PDFs; scroll down as each have multiple pages.

The summary result: If you’re running Postgres, you probably want to do it on DragonFly.  The numbers are the best results for any BSD,  even better to some extent than Linux, which has had its own issues with schedulers and Postgres.  DragonFly 3.2 will include these improvements.

Posted on
Lazy Reading for 2012/10/07

DragonFly 3.2 branches tomorrow if all goes to plan. Until then, I have a lot of reading here for you.

Your unrelated link of the week: Dog Shaming.  I have a parrot, rabbit, and lizard.  They seem like easy, normal pets compared to some of these stories.

 

Posted on
3.2 branch and release plan

As I typed elsewhere, my general plan is to branch DragonFly 3.2 on the 8th, and release on the 22nd.  That should give the recent scheduler and gcc work a chance to settle, and perhaps get a new version of USB support in too.  It will probably be using pkgsrc-2012Q3, also, though we may not have binary i386 packages.  3.2 is shaping up to be a much more significant release than I expected.

 

Posted on
gcc 4.7 in, gcc 4.1 out

John Marino has accomplished the difficult task of putting gcc 4.7 into DragonFly.  Version 4.4 is still the default, and the older 4.1 version has been disabled.  If you want to try this newer version, setting WORLD_CCVER=gcc47 will build kernel and world that way too.  If you’re curious about what’s different in this version of gcc, there’s a 4.7 changelog.

Are we the only BSD with this new a version in base?  I think so.

P.S.: You’ll want to do a full buildworld if you’re running DragonFly 3.1

P.P.S.: you may need to put ‘NO_GCC47=true’ in make.conf, going from IRC comments.

P.P.P.S.: Nope, now it’s fine.