actually, I just did an upgrade from gwt 2.2 to gwt 2.3. I did not realize the AutoBean decode got reworked. I now see a speedup more than 50% =D
On Jul 28, 10:29 am, "Sam J." <[email protected]> wrote: > As you suspected, the bottleneck is indeed elsewhere, very likely in > object creation. > I swapped safeEval with unsafeEval, and that only saved me about > 50-100ms down from 300-400ms. > > Are there any fixes / hacks that can speed up the autobean framework? > > thanks > > On Jul 27, 7:53 pm, Thomas Broyer <[email protected]> wrote: > > > > > > > > > FYI, AutoBeanCodex.decode uses StringQuoter, whose super-source > > implementation (used in compiled code only) uses JsonUtils.safeEval, which > > in turn uses eval() in IE6 to "parse" the JSON, after checking it with a > > couple regexps. So maybe the regexps are slow with large strings? > > You could try overriding the StringQuoter (put your version earlier on the > > classpath) with a version that uses JsonUtils.unsafeEval to see if it makes > > a difference (at your own risks). > > > But AutoBeans do create a lot of objects (an AutoBean and a "wrapper" > > implementing your interface for each object in the JSON), and that could > > really be the bottleneck in your case. -- 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.
