That makes sense. I wasn't sure exactly how the plugin worked and what
javascript was actually running in the browser.
On Thursday, July 10, 2014 1:13:09 PM UTC-7, Jens wrote:
>
> In the meantime though, I'm just frustrated by the fact that I get the
>> performance I want when running in DEV mod
>
> In the meantime though, I'm just frustrated by the fact that I get the
> performance I want when running in DEV mode, but not when it's compiled.
> I'd like to understand is happening in DEV mode that is different from
> compiled that improve performance. Ultimately, the GWT Plugin is servi
Also, I should note that I'm on GWT 2.5.1. We need to upgrade, but are a
little too late in the cycle right now.
--
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 ema
I'll try those compiler settings and see if they help (and make sure they
don't hurt).
And loading a lot of JS/DOM for IE8 is my problem. I'm doing paging and
progressive loading to alleviate the issue. With long running scripts, you
can periodically check in with the main browser event loop to
I think the remaining compiler settings won't buy you a lot additional
performance. The reason why the above settings cost you so much performance
is that the generated JavaScript will be 2x+ the size than what it should
be. Especially recordLineNumbers hurts as GWT will generate one extra line
I have a complex web application that I have to get running under IE8 (no
choice on this). I've been dogged by performance issues for weeks. The
application runs really slow. I get the annoying "Do you want to stop
running this script?" warnings. We've been optimizing for weeks and made
some pr