User bus conclusion

Thiago Macieira thiago at kde.org
Wed Nov 10 23:30:06 GMT 2010


On Wednesday, 10 de November de 2010 21:21:12 Alexander Neundorf wrote:
> > Peak performance at 0.44 ms at roundtrip. Throughput increases with
> > amount of data transferred per call.
> > 
> > If you're making anywhere near 100 calls per second, you're doing
> > something wrong.
> 
> 6 MB/s for local communication is anything but fast.

I said the throughput increases with with the payload size. But D-Bus wasn't 
meant to be a bulk data transport, but instead quick roundtrips.

For an RPC mechanism with structured arguments, topping off at 1000 calls per 
second sounds good to me. But the point is that you shouldn't design apps that 
need that many.

> 100 calls/s is really not much (not in terms of general dbus use-cases, but
> if it claims to be fast).

0.44 ms average round-trip then. Consider you should make one roundtrip only 
and get all the data you need.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20101111/b9926323/attachment.sig>


More information about the kde-core-devel mailing list