[Tilesathome] less inkscape calls in _unstable

Matthias Julius lists at julius-net.net
Wed Sep 24 20:13:08 BST 2008


"Jiri Klement" <jiri.klement at gmail.com> writes:

> Memory shouldn't be a problem for Batik. I have memory limit for java
> set to 1500MB and I have never encountered a tile I couldn't render.
>
> But somebody did a benchmark which showed that batik is much slower
> than inkscape when tile is rendered in one go. It looked like it's
> even slower than when the tile is rendered in stripes by batik.
>
> Actually I did some profiling of batik and the results where quite
> suprising. About 80% of time is spent in method, which copy rendered
> element into resulting image. So it's possible that rendering big tile
> will be actually slower than rendering many small tiles.

That doesn't sound too good.  But, as long as Batik is not bailing out
with those big tiles I am happy for now.  We can re-implement striped
rendering later if necessary.

Matthias




More information about the Tilesathome mailing list