> > If you use emulated stack traces (including line numbers) in current GWT > your app size will roughly increase by 100%. So 45% is a lot better of what > GWT gives you today. >
... Really. I had not seen that mentioned anywhere. What sort of approach does the current emulated stack implementation use, as opposed to the suggested function enter/exit approach? Is there a relative speed hit involved with it too? Because if so, bring on the new implementation ASAP :) On Wednesday, July 17, 2013 7:54:28 PM UTC-4, Jens wrote: > > > I certainly applaud the obvious time, effort, and care that you've put >> into these improvements, but "45% size and 22-44% execution speed overhead" >> sounds like a rather painful penalty to pay. I'm not sure that's going to >> be worth using in a performance-sensitive application. > > > If you use emulated stack traces (including line numbers) in current GWT > your app size will roughly increase by 100%. So 45% is a lot better of what > GWT gives you today. > > > >> Also, how much does this affect compilation time? >> > > This actually shouldn't matter for ordinary compilation. But it would be > interesting to hear in case of SuperDevMode + non SourceMaps browser. > > > -- J. > -- 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 email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
