On Mon, Sep 20, 2010 at 4:35 PM, Eero Tamminen <eero.tammi...@nokia.com> wrote: > For example D-BUS will infinitely buffer messages that are sent > to a connected client but not read by it. If these messages can > be very frequent (say device orientation & network condition messages), > this will soon bloat D-BUS memory usage quite a bit. After D-BUS > starts to swap, it won't perform very well.
Without getting too much into the details, can't dbus be set a threshold for the buffer size so after X events that are still waiting it would stop dispatching and just ignore new incoming events? This can probably prevent it from swapping but will have a cost in the lost events. However, if those events are constantly arriving then my guess is that we can afford to lose them to some degree. (especially if there are network condition messages and orientation events, at most times orientation events acted upon tend to interfere with other uses, while using the number pad to do DTMF while in call) -Sivan _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
