Many thanks, Thomas. I only wish Apple was as responsive as you!... I will be out of the office for a week or so, but I'll give it a try as soon as I return.
thanks again! Scott Ruffner ----- Original Message ----- From: "Thomas DeWeese" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, September 22, 2005 4:46 AM Subject: Re: Applet way too slow on MAC > Hi Andreas, Scott, > > I have created a new bug in Bugzilla to track this issue. > I have also created a patch that replaced the current > DynamicRenderer with one that doesn't touch the underlying > raster data. This should in theory solve the problem for > you on tiger. Since I don't have a Tiger system to check > you will have to try it for me: > > http://issues.apache.org/bugzilla/show_bug.cgi?id=36769 > > There are some edge cases that I know the new renderer > doesn't handle but I'm curious if it solves the problem > at all or in any kind of useful percentage of the cases. > > Andreas Neumann wrote: > > This issue is really annoying. I remember that the performance was much > > better on Panther using the different color model as described in > > > > http://mail-archives.apache.org/mod_mbox/xmlgraphics-batik-users/200508.mbox/[EMAIL PROTECTED] > > > > > > Too bad, to discover that it's slow again on Tiger ... > > > > It would really help if the apple engineers could work on that issue. > > > > Andreas > > > > Thomas DeWeese wrote: > > > >> Hi Scott, > >> > >>> Thomas DeWeese wrote: > >> > >> > >> > >>>> I just noticed Apple released a Java 1.3/1.4 update for > >>>> Tiger. Can you check if this fixes the problem? > >>> > >>> > >> > >> Scott A. Ruffner wrote: > >> > >>> i just installed the Java update on my Powerbook, and it > >>> made no difference in performance -- it's still 20x slower > >>> than under Panther 10.3.9. :( > >> > >> > >> > >> Too bad. > >> > >>> thomas, is there any chance you'll be able to revise how batik > >>> uses BufferedImage/WritableRaster to avoid this performance hit? > >> > >> > >> > >> There is essentially no way to fix this in all of Batik. > >> Much of Batik is built around the java.awt.image.RenderedImage > >> interface. In this interface an image is composed of tiles which > >> are rasters, so you basically can't avoid touching the rasters that > >> are used to build BufferedImages for rendering. > >> > >> There is some chance that the use of Rasters/RenderedImages > >> might be avoided in the 'DynamicRenderer' which would help for > >> simple things but I think that you would find that most content > >> would 'trip' over the raster access. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
