I've spent the last week trying to isolate a GWT 2.6.0 performance regression; every method associated with a split point had an added delay of 30 ms. We finally isolated it to this code splitting change:
-- http://www.gwtproject.org/release-notes.html#Release_Notes_2_6_0_RC1
- GWT.runAsync always runs asynchronously; before it would sometimes be synchronous. (This behavior can be reverted by inheriting SynchronousFragmentLoadCallback.gwt.xml)
That fixed the performance regression, but I'm concerned about this comment in the code -- is SynchronousFragmentLoadCallback going to disappear in GWT 3.0?
https://github.com/gwtproject/gwt/blob/master/user/src/com/google/gwt/core/SynchronousFragmentLoadCallback.gwt.xml
<!-- TODO(goktug): remove after 2.6 is released -->
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment