[Tilesathome] less inkscape calls in _unstable

[Patrick Kilian]

Hi,

> My only issue with removing striped rendering is with memory usage.
Unfortunatly that even strikes with trivial tiles. I tried -unstable
with the tile 123 456 (which is empty see) in xy mode and it failed (by
producing a black tile at z17).

The commandline that produced the black tile was:
LC_ALL=C nice -n10 "inkscape" -z -w 8192 -h 8192
--export-area=0.000000:0.000000:878.906250:878.906250
--export-png="/tmp/tah/12_123_456_0r8b2/tile-z17.png"
"/tmp/tah/12_123_456_0r8b2/tile-z17.svg" >
/tmp/tah/12_123_456_0r8b2/tile-z17.stdout

Running that command produces lots of warnings:
** (inkscape:14998): WARNING **: 268435456 bytes requested for pixel
buffer, I won't try to allocate that.

The box in question has 1.2 GB RAM, which should easily be enough for a
empty tile.  The very same inkscape on the very same box works with
-stable and I was able to render the center of Dresden.

Reducing the -w and -h to 4k gets rid of the warnings and creates a
correct blue tile. (Just like the z16 one). During that rendering
inkscape needs 100-130 MB of RAM.

The osm data and svg are too big to be attached but are available on
request.



Patrick "Petschge" Kilian