Still I'm quite interested why we've never run in similar compilation issues despite having quite a larger set of frontend code as stated in this thread. Can someone explain?
Because you have way less code split points. A lot of code split points will significantly increase compilation time and memory usage. If I do not misunderstand the table posted by the person who started the discussion, the code in question had nearly 800 split points. Maybe the algorithm in GWT compiler can be optimized but currently if you have that many split points GWT compilation will be resource hungry.
-- J.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/d8939562-c2ef-4ebf-8916-e33c9a6d0bcen%40googlegroups.com.
No comments:
Post a Comment