"Ed Loach" <[EMAIL PROTECTED]> writes: > I just tried unstable. I had to add Java to my Virtual machine. And > I can't test it. Every request fails at the Inkscape call line with > an error I reported on this list previously that I get occasionally > which I thought is down to MaxTilesetComplexity. Except on unstable > on the German XP Pro virtual machine I get it every time. 1144,1366 > doesn't look a particularly complex tile. The stable client was > running quite happily with 128MB RAM (at least for the first > request), but the failures below are after I've increased the memory > of the virtual machine to 1GB.
To reduce Inkscape calls the _unstable client renders the PNG for each zoom level in one piece by default. On machines with enough memory this results in a significantly reduced render time. On machines with not enough memory Inkscape craps out. :-( If this happens you can try to set RenderStripes to a positive number. RenderStripes=1 restores the old behavior and RenderStripes=5 only renders zoom level 5 (the 6th zoom level, counting starts with 0, normally z17) in four stripes. If the stable client could render z17 tiles RenderStripes=3 should be save, but RenderStripes=4 or 5 might be worth a try. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
