Google Web Toolkit News - onGWT.com

To content | To menu | To search

Tag - performance

Entries feed - Comments feed

Wednesday 5 March 2008

High Performance Ajax with GWT

image infoq.com :

Today, InfoQ publishes a sample chapter "Integrating with a GWT-RPC Servlet"  from "Google Web Toolkit", a book authored by Ryan Dewsbury.

The Google Web Toolkit (GWT) provides a significant boost to Ajax development. Any new technology like this is a hard sell especially when there are many other choices. In reality, nothing gives you the benefits GWT gives you for Ajax applications. If you're not already bound to a framework it just doesn't make sense to not use it. By using GWT for your Ajax application you get big performance gains for free.

High Performance Ajax with GWT

Thursday 14 February 2008

GWT : improving performance

 

Renat Akhmerov, Sergey Dryganets, Alexey Kharlamov

Our team has used Google Web Toolkit since the 1.1 release. While we are very happy with overall development experience we have found several performance limitations of the library. Actually, the limitations originate from restrictions inherited from the HTML layout algorithms and browsers implementations. In this article we will try to offer ways to workaround these limits by using more effective ways of HTML manipulations.

GWT: improving performance

 

image

Saturday 10 March 2007

Concern regarding GWT compiled html file size

Vish Ramineni

I have been planning to migrate a business application from C#/ASP.Net to the Java world. After spending a lot of time looking at different frameworks, I have decided upon GWT. I have put together a layout and app framework, where I can quickly add pages and interact with JBoss EJB. With only a fraction of the total work done, the file size is already 311 KB. Should I be concerned about the size at all? Are there any guidelines on how to keep the file size under check? At this point, other than this concern, I'm pretty happy with GWT.

Very interesting answer from Dan Morill

Concern regarding GWT compiled html file size


Wednesday 24 January 2007

GWT : JavaScript Memory Consumption

Memory leak issues like this is one of the many reasons we ended up building GWT in the first place. It's possible to characterize exactly which constructs do and do not cause leaks, but it's really tricky to maintain real code without causing them accidentally. And as you probably noticed, when you leak one object you tend to leak many of them because they all reference one-another.
JavaScript Memory Consumption

Sunday 21 January 2007

Google Web Toolkit. Performance Test

Valery&Galina  :  As a part of evaluation of presentation layer frameworks, we performed load tests for the Google Web Toolkit. We used sample application DynaTable, shipped with the GWT. We deployed DynaTable application to Tomcat Server. We recorded test scripts using Grinder TCPProxy. The test methodology is described in this post.
Google Web Toolkit. Performance Test