-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiling with GWT 2.7.0 much much slower (3x) than with GWT 2.6.1 #8960
Comments
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by
|
Reported by |
Reported by
|
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by
|
Reported by |
Reported by
|
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
Reported by |
I haven't seen any progress related to the SDM fix. Since Chrome is dropping classic DevMode support in the next version, I get a bit nervous... |
I have a tentative patch that addresses the code path shown in the stack traces above: https://gwt-review.googlesource.com/13953 Can someone try it and confirm whether it fixes the problem or not. |
Hi Roberto, |
This patch: - caches the set of unresolvable types to avoid file scanning, however the cache is cleared between generator invocations (generators may generate one of the missing files). - resolves inner classes by binary name, avoiding looking for files in subdirectories. Change-Id: Ic848d63f81400effdc92fa50f60e1e63200eed19 Bug-Link: #8960
Hi Roberto, |
Please open another bug with details if the you see other performance problems. |
Using the G1GC garbage collector on OSX made a big difference for me |
Originally reported on Google Code with ID 9006
Reported by
marc.durand
on 2014-11-20 15:24:11The text was updated successfully, but these errors were encountered: