[Tilesathome] Striped rendering is back
Matthias Julius
lists at julius-net.net
Mon Sep 29 14:38:26 BST 2008
Patrick Kilian <osm at petschge.de> writes:
> stable:
> real 0m23.929s
> user 0m15.533s
> sys 0m0.688s
>
> unstable: (RenderStripes = 0)
> breaks after 1m50s
>
> unstable: (RenderStripes = 1)
> real 1m58.567s
> user 1m37.322s
> sys 0m12.201s
>
> unstable: (RenderStripes = 4)
> real 2m37.587s
> user 2m2.480s
> sys 0m23.581s
>
> unstable: (RenderStripes = 5)
> real 6m13.988s
> user 4m32.269s
> sys 1m20.893s
Are you using Inkscape or Batik?
Although I said that RenderStripes = 1 does the same as the client has
done before the difference with current _unstable is that it always
renders the whole tileset. Previously the client was assuming all
zoom levels are empty if the top level (z12) is empty and it skipped
rendering of the other zoom levels. This explains the difference in
user time above.
The other numbers are inverse on my machine. That is RenderStripes =
5 is much faster that RenderStripes = 1. But this is on a system with
8 GB of memory.
Did you actually try the numbers in between? I could imagine the
optimum is somewhere there.
Matthias
More information about the Tilesathome
mailing list