Speed of Krita 2.4

[Dmitry Kazakov]

> 1) Recently, we activated a new setDirty(QVector<QRect>) signals, so it

> > might be a reason. To check this you can edit
> KisPainter::takeDIrtyRegion()
> > to return a united rect instead. But you'll need some stable method of
> > measurement for this.
>
> That could indeed be a candidate. It replaced a patch where we used QRegion
> which definitely caused a slowdown. Using the unified rect, however, slows
> down mirrored and two-handed painting badly. We could probably make this
> conditional if it's really the problem.
>

Better just tweak the parameters of the optimizer ;)



> > 2) I had such problem when I forgot to disable assert checks and tested
> > Dedug build =). RelWithDebInfo should be ok, I guess (Cyrille will
> correct
> > me if i'm wrong =) )
>
> KritaDevs should be good: it has asserts, debug symbols and optimizations.
> There's a huge difference between unoptimized and optimized builds.
>

About a year ago, valgrind showed much time spent on asserts, maybe it might
be better to avoid this.

-- 
Dmitry Kazakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kimageshop/attachments/20110730/5a76c9bf/attachment.htm