Re: Code splitting size analysis

Try -compileReport unless that's what you meant. If there is a lot of
code shared between the different modules then code splitting won't
give you the great results you're hoping to get. As I believe he
documentations says, code splitting is an iterative process of getting
a compile report , seeing what is included where you don't expect it,
and trying to eliminate that.

On Jan 12, 4:26 pm, Sergey <shvets.s...@gmail.com> wrote:
> Hi!
>
> I'm developing some application and recently realized that it's size
> is too big (nearly 1,5MB per browser permutation) and decide to use a
> code splitting feature. But when I split one of my 5 modules to be
> load first it just take 60% of size, so it is not super efficient.
> My question is - how can I know what code exactly are going to be
> split and what not?
> Compiling with -htmlReport is not answering this question, or mb I
> didn't notice some features?
>
> Thanks,
> Sergey.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.