[Tilesathome] Bug in code for batik=2

[Henry Loenwind]

Hi,

CoreDuo 2.4GHz, 2GB Ram here, but with WindowsXP, that could make a big 
difference in regard to inkscape. Even starting it without any 
parameters takes almost 5 seconds before anything happens.

For batik, with the default Java settings I benchmarked 6.5 seconds for 
a single batik run (on a random leftover svg in tah's working dir). 
After I tweaked it, it only took 3.8 seconds.

jdk1.6.0_06/bin/java -client -Xmx1536M -Xms256M

The "-client" switch is the important one. Default is the server engine, 
that one runs faster but has much longer startup times. And with such 
short jobs, that matters. Lowering "-Xms" also help with startup time, 
until you hit the average memery need (allocating to much memory at 
startup takes time, but allocating small chunks during the runtime also 
takes time)

cu
Henry

Jiri Klement wrote:
> I have different results. My home tileset (2226,1397) rendered with
> batik in 18 minutes, with inkscape 8 minutes. Tileset 3638,1613 with
> batik 77m, with inkscape 44m.
> 
> Tested on Gentoo, Inkscape 0.46-r2, batik 1.6-r3, java 1.6.0.05.
> CoreDuo laptop with 3GB ram.
> 
> Is this normal or there is something wrong with my java/batik?
> 
>> Dirk-Lüder Kreie wrote:
>>
>>> I think I have spotted the offending line and fixed it, but someone else
>> Thanks, now it's working. Let's see: My "home tileset" rendered with
>> inkscape: 24 minutes and 43 seconds. Same with batik: 12 minutes 20
>> seconds. Um, is there any reason to use inkscape?
>>
>> cu
>> Henry
> 
> _______________________________________________
> Tilesathome mailing list
> Tilesathome at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/tilesathome