Much to our surprise the test show a quite large performance hit. For example a simple test running three for loops inside each other took almost 50% longer with 2.7 then with 2.6.1.
What work are you doing inside these for loops? If these loops are empty or only do local, useless work it might be a bug in code pruning, e.g. GWT 2.6.1 has removed the for loops from the final output while GWT 2.7 keeps them. You can check that by comparing the final JS output (compile with mode PRETTY).
Can't remember any commit to GWT that might cause a 50% performance drop, especially as GWT now has a new benchmark system in place to detect performance regressions.
-- J.
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/d/optout.
No comments:
Post a Comment