Hi the.networker,
> I have 22,500 rectangles with size of 4 x 4. Whenever public void > updateCompleted(UpdateManagerEvent e) is invoked, I use a thread to send a > new task to the RunnableQueue. That task changes the (x, y) of every one of > the rectangles. As Thomas already hinted, without enough information it's hard to help much. Providing a bit of background on what you are trying to do [1] could also be a lot better in terms of receiving valuable feedback... What you're trying to do can usually be accomplished in several different ways. > It takes about 8 seconds on average to complete one full cycle (document > update, rendering, etc.). The DOM update accounts for 30 - 35% of the time > spent. This is not bad at all. :-) You may also experiment with (un)suspendRedraw [2] and see if there's some improvement, although I'm convinced that performing updates in the update manager (the recommended method which seems already in practice) has the same effect. > My question is: do you think whether I have reached the limit of the Batik > performance or not? Did anyone do better before? Creating and attaching a sample application would help others sharing their results: these values can be tightly related to a given operating system and/or configuration (JVM differences...). Also, please provide more environmental information such as operating system, Batik release (or revision), etc. in a follow-up. Hope this helps, Helder [1] http://www.catb.org/~esr/faqs/smart-questions.html#goal [2] http://xmlgraphics.apache.org/batik/javadoc/index.html?org/apache/batik/bridge/SVGSVGElementBridge.html --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
