Network performance comparison

In what can be described as perfect timing, Sepherosa Ziehau has produced a document comparing FreeBSD, several different Linux kernels, and DragonFly, for networking.  He’s presenting it in the afternoon track of Day 3 for AsiaBSDCon 2017, starting later this week.

He’s published a snippet as a PDF (via), which includes some graphs.    The one place Linux outperforms DragonFly seems to be linked to the Linux version of the network card driver being able to access more hardware – so DragonFly should be comparable or better there too, once the powers-of-2 problem is solved.  (This already came up in comments to a post last week.)

Those graphs are available standalone, too, which means it’s easier to see the fantastic performance for latency – see the thin blue line – that seems exclusive to DragonFly.   That, if anything, is the real takeaway; that DragonFly’s model has benefits not just to plain speed but to the system’s responsiveness under load.  “My CPU is maxed out cause I’m doing a lot of work but I hardly notice” is a common comment over the past few years – and now we can see that for network performance, too.

Lazy Reading for 2017/03/05

A little meta, this week.

Your unrelated tea link of the week: In Sri Lanka’s Tea Paradise, A Social Enterprise Is Brewing.  I actually heard about the quality of the tea (very good) before I heard about the way the company was formed.  Consider where your next tea purchase comes from, in light of this.

In Other BSDs for 2017/03/04

Slightly short this week, maybe because people are prepping for AsiaBSDCon?   I have plenty of links for tomorrow’s Lazy Reading.

Kernel modules in rc.conf, not loader.conf

The longstanding practice is to load kernel modules in loader.conf, as early as possible.  That’s good, for anything that needs them.

However, that also can be bad.  Your machine can be unbootable if there’s a problem with a module or loader.conf is messed up, since that file is read long before the startup process finishes.  Enter the new alternative: modules can be loaded in rc.conf, and the only loader.conf modules needed are those required by / to mount.