It's a known issue. The NPAPI plugin has to cross an IPC boundary to get at the page, and we have to attach an expando onto every java object because Chrome's NPAPI implementation fails to preserve object identity. We're hoping the object identity bug will get fixed someday, but the IPC is unavoidable.
There's not a whole lot you can do to improve performance on your end. If you can avoid making lots of JS/Java boundary crossings in your application, that will speed things up a bit. On Thu, Jan 20, 2011 at 2:47 PM, Bryan Donnovan <bryandonno...@gmail.com>wrote: > When running in DevMode using FF 3.6 or IE8, performance is pretty > good. By performance, I mean the time it takes to refresh the page > containing the GWT app. > > When running in Chrome 8 or 9, reload takes much longer, uses more > cpu, etc. I expect that this has something to do with the process per > tab model of Chrome, and maybe spawning a new process on a page > refresh. > > Is there anything I can do to improve performance running in DevMode > under Chrome? > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-toolkit@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
