[Kde-pim] collectionStatusChanged throttling (was K3Process should be replaced by QProcess)

[Volker Krause]

On Tuesday 22 May 2007 17:14:24 Sam Bishop wrote:
> Volker Krause wrote:
> > akonadi/libakonadi:
> > Add throttling to the collectionStatusChanged() signal in
> > Akonadi::Monitor, ie. instead of emitting this signal directly, keep a
> > list, remove duplicates and use a timer to emit the signals every few
> > msecs. This will improve performance quite a lot when adding many items
> > to a collection at once, since now for every new item the total and
> > unread mail count is retrieved. With throttling the signal emission it
> > will ideally just be a single time.
>
> I'll claim this one.  Volker, I have an additional optimization idea.
> If fetchCollectionStatus is false, an empty CollectionStatus object is
> created and passed as the second argument.  Would it make sense to have
> a class-static, dummy CollectionStatus object made just for that
> purpose?  I'll make that change too, if you'd like.

Great. You might also want to have a look at Collection::root(), currently it 
creates a root collection object for every call, so it could use a similar 
optimization.

regards
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20070524/bd556923/attachment.sig>
-------------- next part --------------
_______________________________________________
kde-pim mailing list
kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/