ginormous performance issue

[Marco Martin]

On Thursday 16 July 2009, Marco Martin wrote:
> On Thursday 16 July 2009, Aaron J. Seigo wrote:
> > On Thursday 16 July 2009, Marco Martin wrote:
> > > but a sick idea come to my mind: what about encoding the pointer value
> > > (or another random number, whatever) into the key? :p
> > > a key will have the form
> > > 7635865:path_300_200_blahblah
> >
> > how will this work between sessions? (new pointer values)
> > between objects with the same svg at the same size? (should share the
> > same cache values)
>
> tomorrow I'll try another approach: putting the delayed save in just Svg
> and use that from FrameSvg, to avoid the code duplication there was before

here it is
since i really didn't want to add new protected members i did this dirty thing 
with accessing svg private in framesvg..
it seems quite a big change to backport tough :)
and still, in the case of an applet with many subwidgets, independent timers 
can do really a big signal storm, so i still kinda like more the pointer 
approach :p
-- 
Marco Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: delayedcache_separatetimers.diff
Type: text/x-patch
Size: 29620 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20090717/b3fb5168/attachment-0001.diff