"DBus Embedded" - a clean break

David Zeuthen zeuthen at gmail.com
Thu Jan 20 09:17:07 PST 2011

Hey Rob,

On Thu, Jan 20, 2011 at 3:09 AM, Rob Taylor <rob.taylor at codethink.co.uk> wrote:
> Has anyone done benchmarks on GDBus vs libdbus serialisation performance?

Yes, GDBus in its currently unoptimized form is about 4x slower than
libdbus (I think - the way this is measured is very sketchy). See here
for details


GDBus performance optimization patches welcome etc. etc. but note that
the GDBus author (which is me) does not agree there's necessarily a
performance problem with GDBus or libdbus. And please note: GDBus
certainly wasn't written because of "performance" problems - it was
written to make it easier to use D-Bus from (multi-threaded) GLib
applications. And I think it pretty much succeeded at that.

Anyway, FWIW, my view is very simple: use the right tool for the right
job etc. etc. In particular, if you want performance, use your own
protocol that can be optimized in any direction you want (hard to do
with standardized protocols like D-Bus). IOW: trying to "optimize"
D-Bus (either libdbus or GDBus) is not what you want - what you want
is a bit more intelligence when designing apps than just saying "let's
hammer all the shit through D-Bus" or "let's expose all the innards of
my app as D-Bus objects and properties". [1]


[1] : I'm not trying to belittle anyone here - I've done all these
mistakes with D-Bus myself

More information about the dbus mailing list