>>>>> "MT" == Milan Trninic <[EMAIL PROTECTED]> writes:
MT> 3. Turns out the speed of Batik is very good. For example, with
MT> 10,000 squares it takes 3 seconds for batik to do it. So,
MT> basically for the varying number of <path> elements displayed (100
MT> - 10, 000) the time spent was 0-3 sec.
MT> 4. But then goes the complicated part - After it was announced
MT> that the setting of the svg document is done, and basically my
MT> small test program has finished, java starts rendering that on
MT> the screen (so nothing is visible yet), and that part is
MT> trouble. Here are the times for it:
MT> 1000 items 4 sec
MT> 2000 items 8 sec
MT> 3000 items 15 sec
MT> 4000 items 30 sec
MT> 5000 items 65 sec
MT> Has anyone worked with something similar. Anybody has any
MT> suggestion?
You don't say what version of Batik you are working with. If you
didn't use the _very_ latest CVS I would suggest you do so. A week or
so ago we fixed a significant performace issue for the initial
rendering that might well cause your doubling behaviour (we were using
Area to calculate the bounds for graphics items which as the Area
get's more complex will slow down, concievably giving the doubling
behavour you saw).
I hope this helps.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
