[Tilesathome] less inkscape calls in _unstable

[Matthias Julius]

"David Lynch" <djlynch at gmail.com> writes:

> My only issue with removing striped rendering is with memory usage.
>
> I'm running the stable version and was assigned a very dense tileset
> earlier in the evening (central Helsinki, complexity over 13 million
> according to the number returned by the server.) I saved the SVG
> output to test, and the Inkscape process rendering the full zoom 17
> image (at 8196x8196) took about 2.5GB of memory, which is a huge
> amount for something that runs (for me, at least) in the background.
>
> Maybe the most complex files should be split up. Rendering one quarter
> of that file (half the height and half the width) seemed fine.

Did you compare this with the stable client?  How much memory is
Inkscape using there?

The assumption so far is that Inkscape is rendering the whole SVG
anyway and the cropping it to the part of the image it was asked for.
If this is true it should consume just as much memory for the striped
rendering and then do it 32 times.

Do you know how much memory it used for z16?  A 8196 pixel RGBA image
should consume 256 MB of memory.  This is only a tenth of the memory
usage you have seen.  I suspect the memory usage is more dependant on
the complexity of the SVG than it is on the size of the output image.

Does anyone has numbers for Batik?

Matthias