4.5 - Activities

[Aaron J. Seigo]

On March 10, 2010, Ivan Čukić wrote:
> > there's also a penalty for keeping the cache in sync across multiple
> > clients.
> > 
> > the other concern is memory usage due to having that cache around ...
> 
> The cache is in the kded service - so no need to sync anything. Or I
> misunderstood you? So the memory overhead is not big at all.

ah, and it's transfered over dbus to the client app on each call?

> > i'd really suggest keeping in mind how a cache can be implemented, ensure
> > the API doesn't prevent that, and then implement the "naive" approach
> > first and measure it from there.
> 
> Well. this change can be trivial - comment out the QHash that stores the
> info. But I still don't think it is a good idea - even when there is only
> 1 second per query, it would be slow - just imagine now that switching
> virtual desktops has a > 1 second lag.

yes, that wouldn't be optimal. does the query really take 1s though? is the 
query itself properly optimized?

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks