I admit I might have found this issue had I had the time pre-GA of GWT
1.5, but alas, better late than never.
I wanted to get a feel for code reduction metrics with GWT 1.5 compile
vs. GWT 1.4 compile. I was expecting a code reduction in size--but my
code size has actually BLOATED with GWT 1.5. I cannot figure out why.
First, I can see with DETAILED compile about a 10% increase in size:
1.4 example size:
4,669,617 9A8641D1F3FE030D2063A0126F143E32.cache.html
1.5 example size:
5,142,200 4B66E1A29D02A04D90E9D9D3EF249299.cache.html
I ruled out several new class sizes that were pulled in due to
serialization of java.util.Map and java.util.Date (ie.
IdentityHashMap, LinkedHashMap, java.sql.Timestamp, etc.), as these
were only about 25K of code.
I've scanned through the generated sources and can't pin it down.
Our application is large mostly due to its inclusion of gwt-ext along
with a medium-sized interface set for GWT/RPC. However, I'm not sure
the gwt-ext compilation is the culprit. I'm thinking that method
inlining is the culprit, but want to get a handle on it.
Can anyone tell me what to look at in generating the compilation
output to narrow down why the app is now 10% larger?
Thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
