tiles & memory
boud at valdyas.org
Thu Oct 12 08:11:45 CEST 2006
On Wednesday 11 October 2006 23:54, Cyrille Berger wrote:
> But we really have to do something about the convolution painter, it's
> performance is _catastrophic_. And around half of the time is spend in
> memcpy of the pixels, which is mostly the difference between 1.5 and 1.6.
> That's mostly to solve this problem that boud and me have consider the lock
Yeah, the other half is spent calling convolve in the colorspaces :-)
> As for locking too big area, we can limit size, like preventing the user to
> lock in memory more tiles than the maximum numbers of allowed tiles.
We do need to think about our API, though. Maybe add a system.exit(0) if the
programmer locks too large an area, so he'll know he was wrong before
shipping. That'll larn them!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kimageshop/attachments/20061012/c6a5032b/attachment.pgp
More information about the kimageshop