GWT performance optimization singleton classes, RPC types, server round-trips
Using GWT 2.5, I am currently going through performance optimizations of a reasonable size GWT client application which is served by C# .NET RPC interfaces on the server side. I have been through the Google I/O video and we have made significant impovements by reducing number of widgets and third party library dependencies, introducing split points and reducing round trips etc. There are a few area that I am not sure of that I would like your views on. 1. I have a buttons toolbar (using our custom button which extends GWT Button) which is frequently redrawn based on the state of the aplication and there are about *150 *buttons to select from to add/remove to the toolbar. Currently I have a singleton class per button which extends my custom base button class. How does this translates into JS and whether using singleton classes like this have any impact on the application size and performance? What happens when a singleton button is removed from parent and re-added? Would it stay in memory from the first instantiation for the life time of the app? 2. As I am using .NET on the server side, I am using a simple open source third-party JSON-RPC library to make calls to the server. Is there any thing I can do for example exclude GWT-RPC implementation from the JS to reduce the size? Would blacklisting *.* make any difference? 3. One of the things mentioned in the GWT performance videos was to determine the user-agent on the server and dispatch the appropriate JS to avoid a round trip. However I can not figure out how to compile the application so that I can know which .cache JS file belongs to which browser implemntation unless I compile it for each user-agent one at a time? thanks -- 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/-/IChJavT94oIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT performance optimization singleton classes, RPC types, server round-trips
On Tuesday, December 18, 2012 10:54:06 AM UTC+1, s3cure wrote: Using GWT 2.5, I am currently going through performance optimizations of a reasonable size GWT client application which is served by C# .NET RPC interfaces on the server side. I have been through the Google I/O video and we have made significant impovements by reducing number of widgets and third party library dependencies, introducing split points and reducing round trips etc. There are a few area that I am not sure of that I would like your views on. 1. I have a buttons toolbar (using our custom button which extends GWT Button) which is frequently redrawn based on the state of the aplication and there are about *150 *buttons to select from to add/remove to the toolbar. Currently I have a singleton class per button which extends my custom base button class. How does this translates into JS and whether using singleton classes like this have any impact on the application size and performance? What happens when a singleton button is removed from parent and re-added? Would it stay in memory from the first instantiation for the life time of the app? It's a singleton, so yes it's kept alive until you leave the app. 2. As I am using .NET on the server side, I am using a simple open source third-party JSON-RPC library to make calls to the server. Is there any thing I can do for example exclude GWT-RPC implementation from the JS to reduce the size? Would blacklisting *.* make any difference? If you don't use GWT-RPC you shouldn't have anything related to GWT-RPC in the generated JS. 3. One of the things mentioned in the GWT performance videos was to determine the user-agent on the server and dispatch the appropriate JS to avoid a round trip. However I can not figure out how to compile the application so that I can know which .cache JS file belongs to which browser implemntation unless I compile it for each user-agent one at a time? The xsiframe linker generates a compilation-mappings.txt which you can read on the server-side to generate the appropriate HTML host page (that's assuming all deferred binding properties can be resolved server-side; if you can't, I suppose you'll have to collapse their values: strong permutations are those selected on the server-side, and soft permutations are selected at runtime; see https://code.google.com/p/google-web-toolkit/wiki/SoftPermutations) The problem then is to install the selected permutation. I believe you'll have to use CrossSiteIframeLinker and set-configuration-property name=installScriptJs to use installScriptAlreadyIncluded.js instead of installScriptEarlyDownload.js. Looking at Google Groups, it seems like they're using a variation of CrossSiteIframeLinker where all permutations include the bootstrap code from the selection script. At first glance, I'd say they extended CrossSiteIframeLinker to override shouldIncludeBootstrapInPrimaryFragment to return 'true' (see also the javadoc for this method). I've never tried those approaches, so if you do, can you please get back to me? (to tell me if you succeeded, if I missed something, etc.) -- 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/-/CnkGRNE5QKMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT performance optimization singleton classes, RPC types, server round-trips
Thank you Thomas. I should probably start thinking about changing my button singletons to instantiate them on-demand and discard on detach. Regarding the selection of correct permutation on the server, given the caveats, I may leave this until I become too eager and if I do I will get back to you with the results. regards On Tuesday, December 18, 2012 10:47:01 AM UTC, Thomas Broyer wrote: On Tuesday, December 18, 2012 10:54:06 AM UTC+1, s3cure wrote: Using GWT 2.5, I am currently going through performance optimizations of a reasonable size GWT client application which is served by C# .NET RPC interfaces on the server side. I have been through the Google I/O video and we have made significant impovements by reducing number of widgets and third party library dependencies, introducing split points and reducing round trips etc. There are a few area that I am not sure of that I would like your views on. 1. I have a buttons toolbar (using our custom button which extends GWT Button) which is frequently redrawn based on the state of the aplication and there are about *150 *buttons to select from to add/remove to the toolbar. Currently I have a singleton class per button which extends my custom base button class. How does this translates into JS and whether using singleton classes like this have any impact on the application size and performance? What happens when a singleton button is removed from parent and re-added? Would it stay in memory from the first instantiation for the life time of the app? It's a singleton, so yes it's kept alive until you leave the app. 2. As I am using .NET on the server side, I am using a simple open source third-party JSON-RPC library to make calls to the server. Is there any thing I can do for example exclude GWT-RPC implementation from the JS to reduce the size? Would blacklisting *.* make any difference? If you don't use GWT-RPC you shouldn't have anything related to GWT-RPC in the generated JS. 3. One of the things mentioned in the GWT performance videos was to determine the user-agent on the server and dispatch the appropriate JS to avoid a round trip. However I can not figure out how to compile the application so that I can know which .cache JS file belongs to which browser implemntation unless I compile it for each user-agent one at a time? The xsiframe linker generates a compilation-mappings.txt which you can read on the server-side to generate the appropriate HTML host page (that's assuming all deferred binding properties can be resolved server-side; if you can't, I suppose you'll have to collapse their values: strong permutations are those selected on the server-side, and soft permutations are selected at runtime; see https://code.google.com/p/google-web-toolkit/wiki/SoftPermutations) The problem then is to install the selected permutation. I believe you'll have to use CrossSiteIframeLinker and set-configuration-property name=installScriptJs to use installScriptAlreadyIncluded.js instead of installScriptEarlyDownload.js. Looking at Google Groups, it seems like they're using a variation of CrossSiteIframeLinker where all permutations include the bootstrap code from the selection script. At first glance, I'd say they extended CrossSiteIframeLinker to override shouldIncludeBootstrapInPrimaryFragment to return 'true' (see also the javadoc for this method). I've never tried those approaches, so if you do, can you please get back to me? (to tell me if you succeeded, if I missed something, etc.) -- 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/-/b0AH1s1pPeIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Thanks for the updated comparison. I wanted to point out that the summary line is not always correct. Examples: GXT Render Time: 1ms GWT Render Time: 0ms GXT was 1x faster... and GXT Render Time: 1ms GWT Render Time: 1ms GXT was 1x faster... -Dave On Apr 4, 5:40 am, Fabrice fabrice.ledo...@gmail.com wrote: I do this quickly :http://gxt3vsgwt.appspot.com/ thanks to code source of previous demo, by replacing GXT 2.2.5 with Ext GWT 3.0 Release Candidate (http://dev.sencha.com/deploy/gxt-3.0.0- rc.zip). Performance are better ! On 27 mar, 16:12, dhoffer dhoff...@gmail.com wrote: Regarding GXT I noticed that comparison website is using GXT 2.2.5 yet is comparing with new GWT 2.4, if making GWT 2.4 compliant app one would probably use the new GXT 3.0 which is in beta right now (almost RC)...I wonder how that compairs to GWT 2.4. I hope not worse. -Dave On Mar 27, 6:28 am, dodo dard keratonj...@gmail.com wrote: Thanks Frank, I think that too, GXT make pretty component but very expensive and very big. Btw I found an interesting website : http://gxtvsgwt.appspot.com/after looking at your anwser. Le mardi 27 mars 2012 13:54:52 UTC+2, Frank a écrit : GXT and SmartGWT have bad performance imo. Better to write your own widgets (which takes a lot of time) using vanilla GWT and make them perform better. That is what we did and our GWT projects have very high performance. Op dinsdag 27 maart 2012 11:55:14 UTC+2 schreef dodo dard het volgende: Helo, I've got friends complaining about GWT/GXT (GWT Ext) performances, well I notice that if we put to many component with GXT, there will be a certain waiting time (3-4s) before it got completely loaded. They said that is better to write the application directly with Javascript that may I'm not agreed 100%. So guys, is there any solution, best practice, limitation or restriction using GXT/GWT ? Or it can't be helped ? Honestly is fun using GWT/GXT, but I'm looking a performance solution too. Regards, Bowie -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
What about the gxt 3 licence? I mean we are talking about GWT performace or a gxt3 vs gwt ? El 9 de abril de 2012 09:40, dhoffer dhoff...@gmail.com escribió: Thanks for the updated comparison. I wanted to point out that the summary line is not always correct. Examples: GXT Render Time: 1ms GWT Render Time: 0ms GXT was 1x faster... and GXT Render Time: 1ms GWT Render Time: 1ms GXT was 1x faster... -Dave On Apr 4, 5:40 am, Fabrice fabrice.ledo...@gmail.com wrote: I do this quickly :http://gxt3vsgwt.appspot.com/ thanks to code source of previous demo, by replacing GXT 2.2.5 with Ext GWT 3.0 Release Candidate (http://dev.sencha.com/deploy/gxt-3.0.0- rc.zip). Performance are better ! On 27 mar, 16:12, dhoffer dhoff...@gmail.com wrote: Regarding GXT I noticed that comparison website is using GXT 2.2.5 yet is comparing with new GWT 2.4, if making GWT 2.4 compliant app one would probably use the new GXT 3.0 which is in beta right now (almost RC)...I wonder how that compairs to GWT 2.4. I hope not worse. -Dave On Mar 27, 6:28 am, dodo dard keratonj...@gmail.com wrote: Thanks Frank, I think that too, GXT make pretty component but very expensive and very big. Btw I found an interesting website : http://gxtvsgwt.appspot.com/after looking at your anwser. Le mardi 27 mars 2012 13:54:52 UTC+2, Frank a écrit : GXT and SmartGWT have bad performance imo. Better to write your own widgets (which takes a lot of time) using vanilla GWT and make them perform better. That is what we did and our GWT projects have very high performance. Op dinsdag 27 maart 2012 11:55:14 UTC+2 schreef dodo dard het volgende: Helo, I've got friends complaining about GWT/GXT (GWT Ext) performances, well I notice that if we put to many component with GXT, there will be a certain waiting time (3-4s) before it got completely loaded. They said that is better to write the application directly with Javascript that may I'm not agreed 100%. So guys, is there any solution, best practice, limitation or restriction using GXT/GWT ? Or it can't be helped ? Honestly is fun using GWT/GXT, but I'm looking a performance solution too. Regards, Bowie -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- ISC. Daniel Mauricio Patiño León. Director ejecutivo Liondev S.A. de C.V. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
I do this quickly : http://gxt3vsgwt.appspot.com/ thanks to code source of previous demo, by replacing GXT 2.2.5 with Ext GWT 3.0 Release Candidate (http://dev.sencha.com/deploy/gxt-3.0.0- rc.zip). Performance are better ! On 27 mar, 16:12, dhoffer dhoff...@gmail.com wrote: Regarding GXT I noticed that comparison website is using GXT 2.2.5 yet is comparing with new GWT 2.4, if making GWT 2.4 compliant app one would probably use the new GXT 3.0 which is in beta right now (almost RC)...I wonder how that compairs to GWT 2.4. I hope not worse. -Dave On Mar 27, 6:28 am, dodo dard keratonj...@gmail.com wrote: Thanks Frank, I think that too, GXT make pretty component but very expensive and very big. Btw I found an interesting website : http://gxtvsgwt.appspot.com/after looking at your anwser. Le mardi 27 mars 2012 13:54:52 UTC+2, Frank a écrit : GXT and SmartGWT have bad performance imo. Better to write your own widgets (which takes a lot of time) using vanilla GWT and make them perform better. That is what we did and our GWT projects have very high performance. Op dinsdag 27 maart 2012 11:55:14 UTC+2 schreef dodo dard het volgende: Helo, I've got friends complaining about GWT/GXT (GWT Ext) performances, well I notice that if we put to many component with GXT, there will be a certain waiting time (3-4s) before it got completely loaded. They said that is better to write the application directly with Javascript that may I'm not agreed 100%. So guys, is there any solution, best practice, limitation or restriction using GXT/GWT ? Or it can't be helped ? Honestly is fun using GWT/GXT, but I'm looking a performance solution too. Regards, Bowie -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
That should be *don't use GXT* I pressume... Op woensdag 28 maart 2012 00:51:45 UTC+2 schreef Joseph Lust het volgende: My company just completed a very large intranet UI using GXT. The overall lesson learned was *don't use GWT*. For the most part it was much slower and the model used in GXT did not extend well to our MVP setup. Perhaps GXT 3 has fixed some of these issues, but we don't want to deploy a framework that's still in beta. Sincerely, Joe -- 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/-/2L6eMw7g2WAJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Oops, I meant don't use G*X*T. We've used pure GWT on another project with all bespoke widgets and despite a bleeding edge HTML5/SVG UI with tons of animations, data, and windows, the pure G*W*T examples runs circles around the other, simpler, G*X*T project. Sorry for the confusion, if there was any. Sincerely, Joe -- 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/-/9-8M9aoarnAJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
On Wed, Mar 28, 2012 at 12:51 AM, Joseph Lust lifeofl...@gmail.com wrote: My company just completed a very large intranet UI using GXT. The overall lesson learned was don't use GWT. For the most part it was much slower and the model used in GXT did not extend well to our MVP setup. Perhaps GXT 3 has fixed some of these issues, but we don't want to deploy a framework that's still in beta. the overall lesson was don't use GWT? did you mean that or don't use GXT? ra! Sincerely, Joe -- 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/-/Ur7JlMX0SjMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- inc: http://ars-machina.raphaelbauer.com tech: http://ars-codia.raphaelbauer.com web: http://raphaelbauer.com -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Finally, I've made my application faster. The idea is not using GridRenderer and prepared the model in the server. For example I write img src=http:/foo/toto.jpg/ in the server than create an Image object in the client. Like I said, the target application is IE8 (not very performance), and by doing this I managed to reduce the grid loading time to almost a half. Hope this help. Sincerely, Bowie -- 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/-/OheIURNk64AJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT Performance : Good or Bad ?
Helo, I've got friends complaining about GWT/GXT (GWT Ext) performances, well I notice that if we put to many component with GXT, there will be a certain waiting time (3-4s) before it got completely loaded. They said that is better to write the application directly with Javascript that may I'm not agreed 100%. So guys, is there any solution, best practice, limitation or restriction using GXT/GWT ? Or it can't be helped ? Honestly is fun using GWT/GXT, but I'm looking a performance solution too. Regards, Bowie -- 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/-/z2WivZfhUOsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
GXT and SmartGWT have bad performance imo. Better to write your own widgets (which takes a lot of time) using vanilla GWT and make them perform better. That is what we did and our GWT projects have very high performance. Op dinsdag 27 maart 2012 11:55:14 UTC+2 schreef dodo dard het volgende: Helo, I've got friends complaining about GWT/GXT (GWT Ext) performances, well I notice that if we put to many component with GXT, there will be a certain waiting time (3-4s) before it got completely loaded. They said that is better to write the application directly with Javascript that may I'm not agreed 100%. So guys, is there any solution, best practice, limitation or restriction using GXT/GWT ? Or it can't be helped ? Honestly is fun using GWT/GXT, but I'm looking a performance solution too. Regards, Bowie -- 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/-/7IyvlvceBLUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Thanks Frank, I think that too, GXT make pretty component but very expensive and very big. Btw I found an interesting website : http://gxtvsgwt.appspot.com/ after looking at your anwser. Le mardi 27 mars 2012 13:54:52 UTC+2, Frank a écrit : GXT and SmartGWT have bad performance imo. Better to write your own widgets (which takes a lot of time) using vanilla GWT and make them perform better. That is what we did and our GWT projects have very high performance. Op dinsdag 27 maart 2012 11:55:14 UTC+2 schreef dodo dard het volgende: Helo, I've got friends complaining about GWT/GXT (GWT Ext) performances, well I notice that if we put to many component with GXT, there will be a certain waiting time (3-4s) before it got completely loaded. They said that is better to write the application directly with Javascript that may I'm not agreed 100%. So guys, is there any solution, best practice, limitation or restriction using GXT/GWT ? Or it can't be helped ? Honestly is fun using GWT/GXT, but I'm looking a performance solution too. Regards, Bowie -- 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/-/Gv4FqFlTRqEJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Regarding GXT I noticed that comparison website is using GXT 2.2.5 yet is comparing with new GWT 2.4, if making GWT 2.4 compliant app one would probably use the new GXT 3.0 which is in beta right now (almost RC)...I wonder how that compairs to GWT 2.4. I hope not worse. -Dave On Mar 27, 6:28 am, dodo dard keratonj...@gmail.com wrote: Thanks Frank, I think that too, GXT make pretty component but very expensive and very big. Btw I found an interesting website : http://gxtvsgwt.appspot.com/after looking at your anwser. Le mardi 27 mars 2012 13:54:52 UTC+2, Frank a écrit : GXT and SmartGWT have bad performance imo. Better to write your own widgets (which takes a lot of time) using vanilla GWT and make them perform better. That is what we did and our GWT projects have very high performance. Op dinsdag 27 maart 2012 11:55:14 UTC+2 schreef dodo dard het volgende: Helo, I've got friends complaining about GWT/GXT (GWT Ext) performances, well I notice that if we put to many component with GXT, there will be a certain waiting time (3-4s) before it got completely loaded. They said that is better to write the application directly with Javascript that may I'm not agreed 100%. So guys, is there any solution, best practice, limitation or restriction using GXT/GWT ? Or it can't be helped ? Honestly is fun using GWT/GXT, but I'm looking a performance solution too. Regards, Bowie -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Bowie, One issue that I've found when working with GXT and GWT is that they use different models for drawing the page elements. GWT tends towards attaching the elements into the DOM immediately whereas GXT caches the elements then attaches them in bulk. This will tend to make them appear slow but is really an optimization on the rendering engine because it doesn't have to do a lot of recalculations. --Stevko On Tue, Mar 27, 2012 at 7:12 AM, dhoffer dhoff...@gmail.com wrote: Regarding GXT I noticed that comparison website is using GXT 2.2.5 yet is comparing with new GWT 2.4, if making GWT 2.4 compliant app one would probably use the new GXT 3.0 which is in beta right now (almost RC)...I wonder how that compairs to GWT 2.4. I hope not worse. -Dave On Mar 27, 6:28 am, dodo dard keratonj...@gmail.com wrote: Thanks Frank, I think that too, GXT make pretty component but very expensive and very big. Btw I found an interesting website : http://gxtvsgwt.appspot.com/after looking at your anwser. Le mardi 27 mars 2012 13:54:52 UTC+2, Frank a écrit : GXT and SmartGWT have bad performance imo. Better to write your own widgets (which takes a lot of time) using vanilla GWT and make them perform better. That is what we did and our GWT projects have very high performance. Op dinsdag 27 maart 2012 11:55:14 UTC+2 schreef dodo dard het volgende: Helo, I've got friends complaining about GWT/GXT (GWT Ext) performances, well I notice that if we put to many component with GXT, there will be a certain waiting time (3-4s) before it got completely loaded. They said that is better to write the application directly with Javascript that may I'm not agreed 100%. So guys, is there any solution, best practice, limitation or restriction using GXT/GWT ? Or it can't be helped ? Honestly is fun using GWT/GXT, but I'm looking a performance solution too. Regards, Bowie -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- -- A. Stevko === If everything seems under control, you're just not going fast enough. M. Andretti -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Stevko, Yes I'm aware of that too, but I think is not the problem with caching, is more about how many DOM object generated by GXT. For a simple row in a grid, GXT will produce : a *div ,a table,a tbody, a tr, a td. *And is not only with the Grid. I think that makes GXT heavier than GWT. Bowie -- 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/-/ZJMxBR_zDC8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Not trying to defend GXT or Smart GWT but what kind of applications are you building ? We ve build some pretty large apps with GXT and never had any type of UI performance problems. 2012/3/27 dodo dard keratonj...@gmail.com Stevko, Yes I'm aware of that too, but I think is not the problem with caching, is more about how many DOM object generated by GXT. For a simple row in a grid, GXT will produce : a *div ,a table,a tbody, a tr, a td. *And is not only with the Grid. I think that makes GXT heavier than GWT. Bowie -- 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/-/ZJMxBR_zDC8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Hi Nino, Is a catalog application type, you search, list and modify products. I have to precise some points : - my application will be used largely by IE8. - Not all the screen have a performance problem. - There is some : - screen that contains : 75 input form, 3 grids (well I have warned my client about not using to much components in one page). - A grid with 23 columns that contains at least 10 GridRenderer (well I'm working at it now by using less GridRenderer) . Regards -- 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/-/j_Gkpwxio6cJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Yep - it sounds like GXT grids are overdriving the system. There hardly seems enough room for content with all that markup. If you don't need all the bells and whistles that come with a gxt grid - it would pay to port to lighter weight GWT grids or plain div and css. Stripping out excess forms, element IDs, and css will lighten the load on the rendering engine. On Tue, Mar 27, 2012 at 8:53 AM, dodo dard keratonj...@gmail.com wrote: Hi Nino, Is a catalog application type, you search, list and modify products. I have to precise some points : - my application will be used largely by IE8. - Not all the screen have a performance problem. - There is some : - screen that contains : 75 input form, 3 grids (well I have warned my client about not using to much components in one page). - A grid with 23 columns that contains at least 10 GridRenderer (well I'm working at it now by using less GridRenderer) . Regards -- 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/-/j_Gkpwxio6cJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- -- A. Stevko === If everything seems under control, you're just not going fast enough. M. Andretti -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
My company just completed a very large intranet UI using GXT. The overall lesson learned was *don't use GWT*. For the most part it was much slower and the model used in GXT did not extend well to our MVP setup. Perhaps GXT 3 has fixed some of these issues, but we don't want to deploy a framework that's still in beta. Sincerely, Joe -- 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/-/Ur7JlMX0SjMJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Hi, A grid with 23 columns that contains at least 10 GridRenderer GXT 3.0: All data widgets support cells (instead of renderers) Cells support events and can fire events High performance via flyweight pattern the model used in GXT did not extend well to our MVP setup. for GXT 3.0 (in beta) Models: Support any bean-like object Not forced to implement GXT interfaces Not forced to use GXT model classes Interoperability with RPC, RequestFactor, AutoBean MVP support has changed too. GWT tends towards attaching the elements into the DOM immediately whereas GXT caches the elements then attaches them in bulk. for GXT 3.0: Components create their DOM at construction DOM available immediately Shawn -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance : Good or Bad ?
Seems this whole thread has more to do with GXT than GWT. We have built a large app, part of which runs on the ipad as a fullscreen web app and performance isn't a problem at all. We built most of our widgets ourself to be very efficient and we make use of HTMLPanels and raw html where it makes sense. On Tuesday, March 27, 2012 6:51:45 PM UTC-4, Joseph Lust wrote: My company just completed a very large intranet UI using GXT. The overall lesson learned was *don't use GWT*. For the most part it was much slower and the model used in GXT did not extend well to our MVP setup. Perhaps GXT 3 has fixed some of these issues, but we don't want to deploy a framework that's still in beta. Sincerely, Joe -- 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/-/x-mIdfV0xAEJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance Issues
If you need to dynamically create a lot of rows based on data; have a look at CellTable, instead of building a Grid or FlexTable and putting widgets in there. It's a total shift in how to approach the problem, but it's designed for rendering performance in mind (to be usable on mobile devices, for instance) -- 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/-/mIFFVgJq8KIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance Issues
I'll have to play around with it more. Does it just do paging on the data? A lot of the data we'll be displaying won't be in rows and columns. This was mostly just a test to see how well it would render views under extreme conditions. The cell list could be super useful. Thanks! -- 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/-/6XR6pYKIWS4J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance Issues
I created this little app that will generate a bunch of rows for you. Inside of each row is 5 Labels that pull the date. http://acumeta.coryschulz.com/gwttest/ So type in something like 5000 and it should render pretty fast and give you the amount of time it took. For each row it's just pulling the date and dropping that in there. In Chrome I just got 507 ms on 1 rows. So I guess what I'm trying to say is, that completely alleviates my GWT performance concerns. :) Especially considering that browsers are getting faster and faster at processing javascript with each update. -- 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/-/J3JxDYk9-BIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT Performance Issues
I was wondering if anyone has had any issues with performance in GWT and how you solved it. Right now there is a project I'm working on where I get some json and generate some views and it's maybe 100 items long and GWT takes around 8 seconds to render it in Chrome. I'm concerned because I'm going to be working on a bigger project and was planning on using GWT but now I'm not so sure. On the bigger project it could end up taking 30 seconds or more just to render the views each time they open a new page. I've read about using timers to try and keep the DOM from freezing, but it prolongs the rendering period. Is there any way to improve performance in GWT, or is this just how the framework is? I've done stuff in Sproutcore before and didn't have any issues with performance, but I'm not sure it's the right framework for the project I'll be doing. Any thoughts would help. Thanks in advance! -- 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/-/V3mLBnZLcBsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
RE: GWT Performance Issues
Publish your code. I suspect the problem might be there. Also Chrome in development mode might be slow (or very slow) compare to production where it usually the fastest browser -Sergey From: google-web-toolkit@googlegroups.com [mailto:google-web-toolkit@googlegroups.com] On Behalf Of CSchulz Sent: Tuesday, December 06, 2011 4:33 PM To: google-web-toolkit@googlegroups.com Subject: GWT Performance Issues I was wondering if anyone has had any issues with performance in GWT and how you solved it. Right now there is a project I'm working on where I get some json and generate some views and it's maybe 100 items long and GWT takes around 8 seconds to render it in Chrome. I'm concerned because I'm going to be working on a bigger project and was planning on using GWT but now I'm not so sure. On the bigger project it could end up taking 30 seconds or more just to render the views each time they open a new page. I've read about using timers to try and keep the DOM from freezing, but it prolongs the rendering period. Is there any way to improve performance in GWT, or is this just how the framework is? I've done stuff in Sproutcore before and didn't have any issues with performance, but I'm not sure it's the right framework for the project I'll be doing. Any thoughts would help. Thanks in advance! -- 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/-/V3mLBnZLcBsJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. _ This electronic message and any files transmitted with it contains information from iDirect, which may be privileged, proprietary and/or confidential. It is intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please delete it and immediately notify the sender. _ -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance Issues
Just keep in mind that development mode is really a lot slower than the
final compiled javascript code (development mode in Firefox seems to be the
fastest, Safari is ok, Chrome feels slow).
How do you generate your views?
I am not quite sure but I think something like:
FlowPanel wrapper = new FlowPanel()
for(Person p : persons) {
wrapper.add(new PersonView(person));
}
containerView.add(wrapper)
could have a better performance than:
for(Person p : persons) {
containerView.add(new PersonView(person));
}
because the first example fills the wrapper while it is not attached to the
DOM yet.
-- J.
--
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/-/KZagJXnFXM0J.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance Issues
Yeah, it entirely was running in Eclipse and when I compile the project and publish it, it does run much faster. I always generate the views first and then push the changes out to the DOM in one or two steps because I know that's the fastest way to do it. I just didn't realize how much slower it ran in dev mode. Thanks again! -- 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/-/wTmJGdPxSWUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT Performance
Here is my scenario: 1) I have to query for my data from a third party web service (in XML format), the data can be huge (100 MB). 2) I had implemented the parsing of XML everything in browser, which was making my application sometimes unresponsive. I have started optimizing my application: 3) I have transferred the parsing the parsing to server side with VTD- XML parser which claim to be much faster and also to shift the computation used in parsing XMLs from client browser to server. Now i have to display the parsed data in a tablular/graphical format (Google's Visualization API), which is the best way to move data from server to client? First option I am thinking of is : To make an RPC call and send a vector/list from server to client. Second option is to create a http proxy (which will also work for Same origin policy problem), and send the data from Server to client in JSON format or some kind of Comet programming for HTTP streaming. I am not sure which one would be the best for my application or any other idea ? Thanks in Advance Nix -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance
The cell widgets are designed for presenting such large amount of data.. I think you can try the CellList widget at first http://gwt.google.com/samples/Showcase/Showcase.html#!CwCellList They also allow you optimize the data transfer between server and browser, i.e. you don't have to send all 100MB to the browser at once. On Sun, Oct 17, 2010 at 11:14 PM, Nix nischalda...@gmail.com wrote: Here is my scenario: 1) I have to query for my data from a third party web service (in XML format), the data can be huge (100 MB). 2) I had implemented the parsing of XML everything in browser, which was making my application sometimes unresponsive. I have started optimizing my application: 3) I have transferred the parsing the parsing to server side with VTD- XML parser which claim to be much faster and also to shift the computation used in parsing XMLs from client browser to server. Now i have to display the parsed data in a tablular/graphical format (Google's Visualization API), which is the best way to move data from server to client? First option I am thinking of is : To make an RPC call and send a vector/list from server to client. Second option is to create a http proxy (which will also work for Same origin policy problem), and send the data from Server to client in JSON format or some kind of Comet programming for HTTP streaming. I am not sure which one would be the best for my application or any other idea ? Thanks in Advance Nix -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Performance issue in IE browser.
pal, you could try using IE8 and the profiler it is shipping with to determine which methods are being called (compiling your code first with -pretty) and which one take more time than others. In our project we thus found out that IE was behaving bad on equals() and equalsIgnoreCase() methods which we replaced then by using hashmaps. HTH Dominik On Oct 6, 3:15 pm, Chris Ramsdale cramsd...@google.com wrote: Pal, In regards to speed and load times, there is generally no silver bullet and each browser is wildly different. That said the the browser's Javascript interpreters and rendering engines generally have the greatest impact on application performance. In your case, determining exactly what is causing your app to load 3x times slower on IE is difficult given that FF and IE have completely different JS interpreters (different names depending on what version you are running) and rendering engines (Trident on IE and Gecko on FF). If you would be able to provide the code that is being executed on startup, or some related design doc we may be better positioned to provide some guidance. Thanks, Chris Ramsdale On Tue, Oct 6, 2009 at 6:03 AM, pal venugopal.pok...@gmail.com wrote: We have developed a stand alone web based application using GWT and performance of this application (Page Load time) in Mozilla firefox browser is 3 times better than the IE browser. Any help in improving performance of this application in IE browser would be great help to us. Thanks, Pal --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT Performance issue in IE browser.
That's because the JS-engines of IE browsers are shi... si.. suboptimal. try this js-performance test on different browsers, to see what I mean (also try chrome) http://wd-testnet.world-direct.at/mozilla/dhtml/funo/jsTimeTest.htm The only thing that may come to our rescue is google-chrome frame http://code.google.com/intl/en-EN/chrome/chromeframe/ On Oct 6, 12:03 pm, pal venugopal.pok...@gmail.com wrote: We have developed a stand alone web based application using GWT and performance of this application (Page Load time) in Mozilla firefox browser is 3 times better than the IE browser. Any help in improving performance of this application in IE browser would be great help to us. Thanks, Pal --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT Performance issue in IE browser.
While I agree on the sub par javascript performance of IE forcing users to switch browsers isn't a valid solution in many professional situations. Depending on what your trying to accomplish determines where your going to find the best bang for buck. In my experience the best way to increase performance is to reduce the amount of data your storing in the browser (I mean, don't store any giant lists like 500 index objects, make sure all references to Widgets are removed when your done with them, etc) - the larger IE memory the worse the performance. Reduce redundant calculations. Maybe even some refactoring into some design patterns might help. Maybe try posting some code or design areas you think are bottlenecking your app. On Oct 6, 1:07 pm, Martin.Trummer martin.trum...@24act.at wrote: That's because the JS-engines of IE browsers are shi... si.. suboptimal. try this js-performance test on different browsers, to see what I mean (also try chrome)http://wd-testnet.world-direct.at/mozilla/dhtml/funo/jsTimeTest.htm The only thing that may come to our rescue is google-chrome framehttp://code.google.com/intl/en-EN/chrome/chromeframe/ On Oct 6, 12:03 pm, pal venugopal.pok...@gmail.com wrote: We have developed a stand alone web based application using GWT and performance of this application (Page Load time) in Mozilla firefox browser is 3 times better than the IE browser. Any help in improving performance of this application in IE browser would be great help to us. Thanks, Pal --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT Performance issue in IE browser.
Pal, In regards to speed and load times, there is generally no silver bullet and each browser is wildly different. That said the the browser's Javascript interpreters and rendering engines generally have the greatest impact on application performance. In your case, determining exactly what is causing your app to load 3x times slower on IE is difficult given that FF and IE have completely different JS interpreters (different names depending on what version you are running) and rendering engines (Trident on IE and Gecko on FF). If you would be able to provide the code that is being executed on startup, or some related design doc we may be better positioned to provide some guidance. Thanks, Chris Ramsdale On Tue, Oct 6, 2009 at 6:03 AM, pal venugopal.pok...@gmail.com wrote: We have developed a stand alone web based application using GWT and performance of this application (Page Load time) in Mozilla firefox browser is 3 times better than the IE browser. Any help in improving performance of this application in IE browser would be great help to us. Thanks, Pal --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT performance Testing
Thanks for the reply David, I posted my questions there already, however it is intended to test performance for GWT application, users of that application would be GWT users most of the time. That's the reason I was wondering that users from this group have used it or not? If not what others have used for testing multi user scenario and performance of application. Thanks for the help. Sure, didn't mean to imply that you should post your question here. To simulate concurrent users, I've used JMeter. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT performance Testing
Sure, didn't mean to imply that you should post your question here. shouldn't* -Dave --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT performance Testing
Hi, I came across gwt-debug-panel http://code.google.com/p/gwt-debug-panel/ on google codes and wondering if any one has tried it for performance testing gwt application? Can it be used for simulating multiple users? The project appears to have its own discussion group. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT performance Testing
Thanks for the reply David, I posted my questions there already, however it is intended to test performance for GWT application, users of that application would be GWT users most of the time. That's the reason I was wondering that users from this group have used it or not? If not what others have used for testing multi user scenario and performance of application. Thanks for the help. On Oct 1, 6:43 pm, David Durham david.durham...@gmail.com wrote: Hi, I came across gwt-debug-panel http://code.google.com/p/gwt-debug-panel/ on google codes and wondering if any one has tried it for performance testing gwt application? Can it be used for simulating multiple users? The project appears to have its own discussion group. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
GWT performance Testing
Hi, I came across gwt-debug-panel http://code.google.com/p/gwt-debug-panel/ on google codes and wondering if any one has tried it for performance testing gwt application? Can it be used for simulating multiple users? Thanks in advance for the help. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
GWT performance
Hello All, i am a newbie that want to try to build a web application using GWT, but i heard from some of my colleague that GWT has some issue with its performance (reliability, load slowly). So, is there anyone can enlighten me? Thanks. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT performance
This is not really a GWT-problem. If you're using IE (all versions) ... the Javascript-Engine is the breakman. With all real browsers in actual versions (Firefox, Safari, Chrome, Opera) performance is OK. On Sep 2, 6:32 am, kristian kristian.wij...@gmail.com wrote: Hello All, i am a newbie that want to try to build a web application using GWT, but i heard from some of my colleague that GWT has some issue with its performance (reliability, load slowly). So, is there anyone can enlighten me? Thanks. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT performance
Kristian, Do GMail or the GWT showcase application work well enough for you in your intended browser? If so, then in all likelihood your GWT application will perform adequately. I'm not aware of any reliability issues as such. The only thing that springs to mind is that GWT compiles for specific browsers that it knows about at compile time. Like many other web application technologies, if a new browser comes out then they can break compatibility. Recent examples of this are with IE8 and FF 3.5, however Google have always endeavoured to roll out compiler updates to rectify these issues. Loading times can be a problem and it boils down to a couple of things: 1. I believe IE's JavaScript parser gets disproportionately slower the larger your GWT application is (other browsers do not suffer with this); 2. a compressed GWT application can still be fairly large, say 150k to 200k, which can be an issue if your target audience are all on dial up connections. Remember though that this download is a one-off and the browser will cache that version of the app forever so all subsequent app launches are significantly quicker. Also, GWT 2.0 has a number of things in the pipeline to address these issues (like code splitting). Cheers, Chris. On Sep 2, 5:32 am, kristian kristian.wij...@gmail.com wrote: Hello All, i am a newbie that want to try to build a web application using GWT, but i heard from some of my colleague that GWT has some issue with its performance (reliability, load slowly). So, is there anyone can enlighten me? Thanks. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT performance
Dear All, Thanks for the explanation. Now i have no more doubt to start using GWT. On Sep 2, 5:27 pm, Chris Lowe chris.lowe...@gmail.com wrote: Kristian, Do GMail or the GWT showcase application work well enough for you in your intended browser? If so, then in all likelihood your GWT application will perform adequately. I'm not aware of any reliability issues as such. The only thing that springs to mind is that GWT compiles for specific browsers that it knows about at compile time. Like many other web application technologies, if a new browser comes out then they can break compatibility. Recent examples of this are with IE8 and FF 3.5, however Google have always endeavoured to roll out compiler updates to rectify these issues. Loading times can be a problem and it boils down to a couple of things: 1. I believe IE's JavaScript parser gets disproportionately slower the larger your GWT application is (other browsers do not suffer with this); 2. a compressed GWT application can still be fairly large, say 150k to 200k, which can be an issue if your target audience are all on dial up connections. Remember though that this download is a one-off and the browser will cache that version of the app forever so all subsequent app launches are significantly quicker. Also, GWT 2.0 has a number of things in the pipeline to address these issues (like code splitting). Cheers, Chris. On Sep 2, 5:32 am, kristian kristian.wij...@gmail.com wrote: Hello All, i am a newbie that want to try to build a web application using GWT, but i heard from some of my colleague that GWT has some issue with its performance (reliability, load slowly). So, is there anyone can enlighten me? Thanks. --~--~-~--~~~---~--~~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~--~~~~--~~--~--~---
Simple Sidescroller (browser/GWT performance?)
Using a timer and a clip: rect() I've put together a small scrolling demo. It has coder art and some borrowed clouds and background noise (gwt-voices). Link is here: http://linuxstuff.org/scrolldemo/ - there's no controls yet, just things scrolling by for a minute; uses alpha PNGs, so no IE6. Every 80ms the animation clock ticks and things move; anything finer grained it seemed FF3 wasn't able to keep up. From this experiment, it seems that things Aren't Quite There Yet for doing such things with this stack; which is surprising to me. Anyway, if anyone is interested the code is available at: http://linuxstuff.org/scrolldemo/AnimGWT.tar.bz2 The heart of the code is in MagicScroller.animate(). I'd love to know if there's a better way to be doing this, or if there are any browser profiling tools out there that anyone can recommend. Cheers! JAmes --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
