Krita's rendering model

Boudewijn Rempt boud at valdyas.org
Thu Sep 15 16:14:17 CEST 2005


On Thursday 15 September 2005 16:02, Boudewijn Rempt wrote:
> On Thursday 15 September 2005 15:04, Boudewijn Rempt wrote:
> > On Thursday 15 September 2005 14:59, Casper Boemann wrote:
> > > So either we use the projection for something useful or we just remove
> > > it to save memory.
> >
> > If we keep it, then I have an easier time with the optimized paintContent
> > scheme 2 I outlined in my original mail. I would move composition to the
> > notify method, and paintContent would just use the right bit of the
> > projection. That has an important advantage: compositing no longer has to
> > be done in X11 optimized render chunks, so we can have longer runs of
> > pixels to feed to KisPainter.
>
> I haven't succeeded yet in making the composition dependent upon notify
> and the rendertopainter use the projection, but removing the
> renderheight/renderwidth loop means a 25% speed increase in itself:
>
> With loop:
>
>     painted a 512 x 512 image 100 times: 4397 ms
>     painted a 512 x 512 image with 3 layers 100 times: 4841 ms
>
>
> Without loop:
>
>     painted a 512 x 512 image 100 times: 3298 ms
>     painted a 512 x 512 image with 3 layers 100 times: 3672 ms
>

And when caching the image in the projection, ie, not compositing for every 
view:

* paintView test

    painted a 512 x 512 image 100 times: 2615 ms
    painted a 512 x 512 image with 3 layers 100 times: 2559 ms

-- 
Boudewijn Rempt 
http://www.valdyas.org/fading/index.cgi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kimageshop/attachments/20050915/c8df74dd/attachment.pgp


More information about the kimageshop mailing list