Iterator benchmark
Sven Langkamp
sven.langkamp at gmail.com
Tue Jun 9 19:22:25 CEST 2009
On Tue, Jun 9, 2009 at 1:40 PM, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> > Date: Mon, 8 Jun 2009 22:46:32 +0200
> > From: Sven Langkamp <sven.langkamp at gmail.com>
>
> > I have commited a first version of the iterator benchmark we dicussed
> > yesterday. It basically iterates over a paint device without doing
> memcpys.
> > The results are as we expected:
> >
> > -HLine- and VLineIterator perform quite similar.
> > -the rect iterator about 10% faster than hline
> > -the random accesor is about 40% slower than hline
>
> Could you give some numbers of iterator access/modification in pixel per
> seconds for a non Krita developer.
The benchmark is pretty simple and you should be careful with the actual
numbers. The values change a bit with different system load.
It's just measure how long it takes an iterator to iterate over each pixel
paint device without doing a memcpy. Colorspace is RGB 8.
Running it on a Core Duo 2GHz I get:
HLineIterator 12,5 MPixel/sec
RectIterator 15,3 MPixel/sec
RandomIterator 8 MPixel/sec
With doing a memcpy I get:
HLineIterator 5.8 MPixel/sec
I curious how that compares to other implementations.
>
> thanks in advance,
> Kai-Uwe Behrmann
> --
> developing for colour management
> www.behrmann.name + www.oyranos.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kimageshop/attachments/20090609/9fba4b4f/attachment.htm
More information about the kimageshop
mailing list