[prev in list] [next in list] [prev in thread] [next in thread]
List: freedesktop-dbus
Subject: Re: About performance of D-Bus
From: "Jerome Philbert" <jerome.philbert () gmail ! com>
Date: 2008-11-04 10:59:02
Message-ID: 9c0d19af0811040259p55371b27ib145f378c748bddd () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Is it thinkable to use the very old version of DBus, benchmarked here ?
http://lists.freedesktop.org/pipermail/dbus/2004-November/001779.html
Jerome
2008/11/4 Jerome Philbert <jerome.philbert@gmail.com>
> Hi,
>
> For me, the message speed is important and 4.7ms per message is too slow,
> because :
> - 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.
>
> Jerome
>
>
> 2008/10/31 Simon McVittie <simon.mcvittie@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
>> platform
>> > 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
>> where
>> > many messages are exchanged at the same time; for instance, when the
>> network
>> > connection goes online the Telepathy connection managers must deliver
>> > information on the online contacts, their avatars, a few GetAll methods
>> are
>> > called on the Telepathy connections and channels interfaces to retrieve
>> their
>> > 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
>> altering
>> D-Bus.
>>
>> Simon
>> _______________________________________________
>> dbus mailing list
>> dbus@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/dbus
>>
>
>
[Attachment #5 (text/html)]
Is it thinkable to use the very old version of DBus, benchmarked here ?<br><a \
href="http://lists.freedesktop.org/pipermail/dbus/2004-November/001779.html">http://lists.freedesktop.org/pipermail/dbus/2004-November/001779.html</a><br>
<br>Jerome<br><br><div class="gmail_quote">2008/11/4 Jerome Philbert <span dir="ltr"><<a \
href="mailto:jerome.philbert@gmail.com">jerome.philbert@gmail.com</a>></span><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt \
0.8ex; padding-left: 1ex;"> Hi,<br><br>For me, the message speed is important and 4.7ms per \
message is too slow, because :<br> - 100ms is the max reaction time for the \
user<br> - I have several applications interconnected together through an IPC (will be \
DBus or another)<br>
- that can send several messages in the same time<br><br>In my system, there are \
situations where several applications send several messages in the same time, and it cannot fit \
the 100ms.<br><br>That is why I would be interested by a quicker direct DBus.<br>
<br>Jerome<br><br><br><div class="gmail_quote">2008/10/31 Simon McVittie <span dir="ltr"><<a \
href="mailto:simon.mcvittie@collabora.co.uk" \
target="_blank">simon.mcvittie@collabora.co.uk</a>></span><div><div></div><div \
class="Wj3C7c"> <br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div>On Fri, 31 Oct 2008 at 17:23:16 \
+0200, Alberto Mardegan wrote:<br> > I was not especially thinking of the desktop, but \
rather to the Maemo platform<br> > and Telepathy specifically: for instance, telepathy \
connection managers<br> > typically communicate with 1-2 processes only<br>
<br>
</div>... for very large values of "2" that include Mission Control, the<br>
presence UI, the chat UI, the VoIP UI, and future collaborative stuff.<br>
Sorry, Telepathy is not a good example here!<br>
<div><br>
> Yes, that's true. What I'm more concerned about is those (rare) moments where<br>
> many messages are exchanged at the same time; for instance, when the network<br>
> connection goes online the Telepathy connection managers must deliver<br>
> information on the online contacts, their avatars, a few GetAll methods are<br>
> called on the Telepathy connections and channels interfaces to retrieve their<br>
> properties. This might have some sensible impact on the user experience.<br>
<br>
</div>This could be optimized by cleverer client-side code in telepathy-glib<br>
(I'm already aware of some low-hanging fruit which I'll be working on<br>
soon) and less round-trippy APIs (ditto) before we go anywhere near altering<br>
D-Bus.<br>
<font color="#888888"><br>
Simon<br>
</font><div><div></div><div>_______________________________________________<br>
dbus mailing list<br>
<a href="mailto:dbus@lists.freedesktop.org" target="_blank">dbus@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/dbus" \
target="_blank">http://lists.freedesktop.org/mailman/listinfo/dbus</a><br> \
</div></div></blockquote></div></div></div><br> </blockquote></div><br>
_______________________________________________
dbus mailing list
dbus@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dbus
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic