About performance of D-Bus
jerome.philbert at gmail.com
Tue Nov 4 02:14:50 PST 2008
For me, the message speed is important and 4.7ms per message is too slow,
- 100ms is the max reaction time for the user
- I have several applications interconnected together through an IPC (will
be DBus or another)
- that can send several messages in the same time
In my system, there are situations where several applications send several
messages in the same time, and it cannot fit the 100ms.
That is why I would be interested by a quicker direct DBus.
2008/10/31 Simon McVittie <simon.mcvittie at collabora.co.uk>
> On Fri, 31 Oct 2008 at 17:23:16 +0200, Alberto Mardegan wrote:
> > I was not especially thinking of the desktop, but rather to the Maemo
> > and Telepathy specifically: for instance, telepathy connection managers
> > typically communicate with 1-2 processes only
> ... for very large values of "2" that include Mission Control, the
> presence UI, the chat UI, the VoIP UI, and future collaborative stuff.
> Sorry, Telepathy is not a good example here!
> > Yes, that's true. What I'm more concerned about is those (rare) moments
> > many messages are exchanged at the same time; for instance, when the
> > connection goes online the Telepathy connection managers must deliver
> > information on the online contacts, their avatars, a few GetAll methods
> > called on the Telepathy connections and channels interfaces to retrieve
> > properties. This might have some sensible impact on the user experience.
> This could be optimized by cleverer client-side code in telepathy-glib
> (I'm already aware of some low-hanging fruit which I'll be working on
> soon) and less round-trippy APIs (ditto) before we go anywhere near
> dbus mailing list
> dbus at lists.freedesktop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dbus