I am seeing this issue as well. Very painful. Two minutes to de-serialize 2,300 records on a Core i7. I would use super-dev but gwt-maven-plugin still hasn't released 2.5 yet...
On Monday, June 11, 2012 4:02:50 AM UTC-4, Thomas Broyer wrote: > > > > On Monday, June 11, 2012 9:47:35 AM UTC+2, Marko wrote: >> >> I think this is because of the Java-JavaScript Bridge in the DevMode. >> Application is partially running in Java and partially in JavaScript and >> the communication between the two is relatively slow. Because there are >> many cross-calls between Java and JavaScript within (de)serialization it >> takes so much time... >> >> But I am not an expert on this and I may be wrong... I used to have >> similar problems on one of the GWT apps... >> > > Yes, that, and the use of JSONObject, which creates one JSONValue instance > per value to be serialized. > > Christopher, you'd better call JSON.stringify from JSNI when in Dev Mode. > Either that, or try Super Dev Mode ;-) > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ivqCYlk3tIIJ. 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.
