Million access to GWT Appl ??
18 views
Skip to first unread message
manish kumar
Jun 19, 2010, 10:44:42 PM6/19/10
to Google Web Toolkit
Hi, i have gone through many articles on web and found that GWT is not
good for an application that has million users access simultaniouly.
Is that really true? If not then what should i do make it accessible
by million users?Is that really tough job in GWT?
good for an application that has million users access simultaniouly.
Is that really true? If not then what should i do make it accessible
by million users?Is that really tough job in GWT?
Subhrajyoti Moitra
Jun 21, 2010, 2:21:28 PM6/21/10
to google-we...@googlegroups.com
i dont think this has anything to do with GWT. ITs upto you what mess you make of your code, that it cant support a million users.
U say u have seen "many articles" can u please post some of them here?
In fact, GWT goes to extreme lengths to ensure that the application is optimized and behaves in the desired way.
my 2 cents!!
Subhro.
U say u have seen "many articles" can u please post some of them here?
In fact, GWT goes to extreme lengths to ensure that the application is optimized and behaves in the desired way.
my 2 cents!!
Subhro.
--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Jaroslav Záruba
Jun 21, 2010, 2:25:46 PM6/21/10
to google-we...@googlegroups.com
What was such claim based on? It does sound weird to me.
Client-side, which is where GWT operates mostly, does not care about how many users is accessing your website. By providing things like ClientBundle or code-splitting I think GWT helps your website handle loads of users better.
Jim
Jun 21, 2010, 2:54:21 PM6/21/10
to Google Web Toolkit
The claims must be from .net side. Please post the articles. I do want
to read them.
On Jun 21, 2:25 pm, Jaroslav Záruba <jaroslav.zar...@gmail.com> wrote:
> What was such claim based on? It does sound weird to me.
> Client-side, which is where GWT operates mostly, does not care about how
> many users is accessing your website. By providing things like ClientBundle
> or code-splitting I think GWT helps your website handle loads of users
> better.
>
> On Sun, Jun 20, 2010 at 4:44 AM, manish kumar
> <manish.online2...@gmail.com>wrote:
> > .
to read them.
On Jun 21, 2:25 pm, Jaroslav Záruba <jaroslav.zar...@gmail.com> wrote:
> What was such claim based on? It does sound weird to me.
> Client-side, which is where GWT operates mostly, does not care about how
> many users is accessing your website. By providing things like ClientBundle
> or code-splitting I think GWT helps your website handle loads of users
> better.
>
> On Sun, Jun 20, 2010 at 4:44 AM, manish kumar
>
>
>
> > Hi, i have gone through many articles on web and found that GWT is not
> > good for an application that has million users access simultaniouly.
> > Is that really true? If not then what should i do make it accessible
> > by million users?Is that really tough job in GWT?
>
> > --
> > 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-we...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-web-tool...@googlegroups.com<google-web-toolkit%2Bunsubs cr...@googlegroups.com>
>
>
> > Hi, i have gone through many articles on web and found that GWT is not
> > good for an application that has million users access simultaniouly.
> > Is that really true? If not then what should i do make it accessible
> > by million users?Is that really tough job in GWT?
>
> > --
> > 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-we...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
Jim Douglas
Jun 21, 2010, 3:17:44 PM6/21/10
to Google Web Toolkit
References, please?
The most charitable interpretation of this is that someone is
misinformed.
The most charitable interpretation of this is that someone is
misinformed.
rakesh wagh
Jun 21, 2010, 3:28:18 PM6/21/10
to Google Web Toolkit
You can either drive a nail using hammer or break some one's head! It
really depends on how you use the tool; be it the hammer or gwt.
as far as million access is concerned, it completely depends on your
server if it can handle that load or not. Look into your server side
code, server infrastructure, network limitations, etc.
In your client code you should avoid unnecessary server calls. Or
atleast try to club multiple calls into one(if practically possible).
As far as sluggishness of code is concerned for big size apps, you
should divide your app into modules, use code splitting, etc.
If you compare gwt app with jsp based app:
- jsp app will make server trip for every user application. example
multiple paged data table.
- data being transferred between client and the server is more in case
of jsp, as the entire page has to reload.
- gwt app is usually single page based. Server calls are only made for
data.
- gwt app can execute most logic on client side and use server only to
persist or fetch data.
- In a nutshell, a well written gwt app will always reduce your server
trips and amount of data being transferred when compared to
traditional jsp/struts based applications.
If you compare gwt to other js based toolkits, they all behave similar
as far as client to server communication is concerned. gwt only makes
life simple for the developers.
Rakesh Wagh
really depends on how you use the tool; be it the hammer or gwt.
as far as million access is concerned, it completely depends on your
server if it can handle that load or not. Look into your server side
code, server infrastructure, network limitations, etc.
In your client code you should avoid unnecessary server calls. Or
atleast try to club multiple calls into one(if practically possible).
As far as sluggishness of code is concerned for big size apps, you
should divide your app into modules, use code splitting, etc.
If you compare gwt app with jsp based app:
- jsp app will make server trip for every user application. example
multiple paged data table.
- data being transferred between client and the server is more in case
of jsp, as the entire page has to reload.
- gwt app is usually single page based. Server calls are only made for
data.
- gwt app can execute most logic on client side and use server only to
persist or fetch data.
- In a nutshell, a well written gwt app will always reduce your server
trips and amount of data being transferred when compared to
traditional jsp/struts based applications.
If you compare gwt to other js based toolkits, they all behave similar
as far as client to server communication is concerned. gwt only makes
life simple for the developers.
Rakesh Wagh
Jaroslav Záruba
Jun 21, 2010, 3:42:36 PM6/21/10
to google-we...@googlegroups.com
On Mon, Jun 21, 2010 at 9:28 PM, rakesh wagh <rak...@gmail.com> wrote:
If you compare gwt to other js based toolkits, they all behave similar
as far as client to server communication is concerned. gwt only makes
life simple for the developers.
...and (with comparably complex UI) makes your JavaScript run faster :)
Rakesh Wagh
On Jun 19, 7:44 pm, manish kumar <manish.online2...@gmail.com> wrote:
> Hi, i have gone through many articles on web and found that GWT is not
> good for an application that has million users access simultaniouly.
> Is that really true? If not then what should i do make it accessible
> by million users?Is that really tough job in GWT?
--
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-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
Chris Boertien
Jun 22, 2010, 4:33:15 AM6/22/10
to google-we...@googlegroups.com
Your essentially asking the wrong question. I think its better to
think of by how much will GWT or products similar to GWT reduce the
load on a server.
think of by how much will GWT or products similar to GWT reduce the
load on a server.
You have to consider the fact that every user accessing a traditional
website backed by a templating engine involves alot of resources for
each and every request for new information.
Take a web forum for example. I think they are probably one of the
least effecient communication mediums and would be very interesting to
see a GWT implementation of one. With the status quo web forum you
have full page loads happening every single time a user wants to move
around on the forum. And if the user wants to see what is new on the
forum... you guessed it, full page load.
Now, if you consider all the ways that having most of the web forum on
the client side and using much more lightweight RPC calls to get new
info (and ONLY new info) there would be quite large improvements. I
wouldnt be suprised if the resource requirement of a GWT based web
forum dropped the load on even the most highly active forums by
upwards of 80%, and probably more if you really took the care to setup
some proper caching. But regardless of how the server resource load
would drop, just the bandwidth drop alone would be a 100% win.
2010/6/21 Jaroslav Záruba <jarosla...@gmail.com>:
Olivier Monaco
Jun 22, 2010, 6:03:40 AM6/22/10
to Google Web Toolkit
Yes, but think that user will ask for more interactivity... resulting
in more requests. But, of course, bandwidth, CPU and memory will be
saved. They will be saved more is a good architecture is used like a
Rest-like server, I think.
Olivier
On Jun 22, 10:33 am, Chris Boertien <chris.boert...@gmail.com> wrote:
> Your essentially asking the wrong question. I think its better to
> think of by how much will GWT or products similar to GWT reduce the
> load on a server.
>
> You have to consider the fact that every user accessing a traditional
> website backed by a templating engine involves alot of resources for
> each and every request for new information.
>
> Take a web forum for example. I think they are probably one of the
> least effecient communication mediums and would be very interesting to
> see a GWT implementation of one. With the status quo web forum you
> have full page loads happening every single time a user wants to move
> around on the forum. And if the user wants to see what is new on the
> forum... you guessed it, full page load.
>
> Now, if you consider all the ways that having most of the web forum on
> the client side and using much more lightweight RPC calls to get new
> info (and ONLY new info) there would be quite large improvements. I
> wouldnt be suprised if the resource requirement of a GWT based web
> forum dropped the load on even the most highly active forums by
> upwards of 80%, and probably more if you really took the care to setup
> some proper caching. But regardless of how the server resource load
> would drop, just the bandwidth drop alone would be a 100% win.
>
> 2010/6/21 Jaroslav Záruba <jaroslav.zar...@gmail.com>:
in more requests. But, of course, bandwidth, CPU and memory will be
saved. They will be saved more is a good architecture is used like a
Rest-like server, I think.
Olivier
On Jun 22, 10:33 am, Chris Boertien <chris.boert...@gmail.com> wrote:
> Your essentially asking the wrong question. I think its better to
> think of by how much will GWT or products similar to GWT reduce the
> load on a server.
>
> You have to consider the fact that every user accessing a traditional
> website backed by a templating engine involves alot of resources for
> each and every request for new information.
>
> Take a web forum for example. I think they are probably one of the
> least effecient communication mediums and would be very interesting to
> see a GWT implementation of one. With the status quo web forum you
> have full page loads happening every single time a user wants to move
> around on the forum. And if the user wants to see what is new on the
> forum... you guessed it, full page load.
>
> Now, if you consider all the ways that having most of the web forum on
> the client side and using much more lightweight RPC calls to get new
> info (and ONLY new info) there would be quite large improvements. I
> wouldnt be suprised if the resource requirement of a GWT based web
> forum dropped the load on even the most highly active forums by
> upwards of 80%, and probably more if you really took the care to setup
> some proper caching. But regardless of how the server resource load
> would drop, just the bandwidth drop alone would be a 100% win.
>
Stefan Bachert
Jun 22, 2010, 9:54:13 AM6/22/10
to Google Web Toolkit
Hi manish,
the opposite is true.
An AJAX/GWT-approach reduces dramatically the load from the servers.
I showed in an estimation that with GWT/AJAX a server is able to drive
10-50 times more clients, compared to classical web technology like
JSP, JSF
So using GWT is also a green IT topic.
The german reading audience may look at
http://gwtworld.de/bin/Offen/Strom%20sparen%20mit%20GWT
Till now I do not see any technology which is using energy and
performance more efficient and responsible than GWT.
I dont know exactly how many users are using Google wave. Google wave
is a GWT application, it is fast, and I guess it has millions of
users.
When you are really going to develop an applications for millions of
users, you urgently should use GWT.
Stefan Bachert
http://gwtworld.de
the opposite is true.
An AJAX/GWT-approach reduces dramatically the load from the servers.
I showed in an estimation that with GWT/AJAX a server is able to drive
10-50 times more clients, compared to classical web technology like
JSP, JSF
So using GWT is also a green IT topic.
The german reading audience may look at
http://gwtworld.de/bin/Offen/Strom%20sparen%20mit%20GWT
Till now I do not see any technology which is using energy and
performance more efficient and responsible than GWT.
I dont know exactly how many users are using Google wave. Google wave
is a GWT application, it is fast, and I guess it has millions of
users.
When you are really going to develop an applications for millions of
users, you urgently should use GWT.
Stefan Bachert
http://gwtworld.de
Blessed Geek
Jun 23, 2010, 2:41:12 AM6/23/10
to Google Web Toolkit
You know that cows (and deer too) chew their cud. Cows have a
secondary stomach, so it could store whatever grass it has chewed off
the field in the 2ndary stomach. Then it could regurgitate the stored
cud and chew on it afterwards.
Your question is akin to saying that you read an article that says
that the delivery of food (cows like alfalfa, I'm told) to cows is not
efficient when there are more than a million cows in a dairy farm, the
reason being cows chew their cud.
What has cows chewing their cud got to do with the efficiency of
delivery of food to cows. It is the fault of the delivery system and
has nothing to do with whether a cow chews its cud. The efficiency of
delivery is the same whether there are a million cows or a million
kangaroos.
Obviously, the article you read is erroneous and/or its author has a
huge grudge against Google.
Likewise, GWT allowing a browser to chew on its cud does not dictate
the efficiency of the data delivery system.
secondary stomach, so it could store whatever grass it has chewed off
the field in the 2ndary stomach. Then it could regurgitate the stored
cud and chew on it afterwards.
Your question is akin to saying that you read an article that says
that the delivery of food (cows like alfalfa, I'm told) to cows is not
efficient when there are more than a million cows in a dairy farm, the
reason being cows chew their cud.
What has cows chewing their cud got to do with the efficiency of
delivery of food to cows. It is the fault of the delivery system and
has nothing to do with whether a cow chews its cud. The efficiency of
delivery is the same whether there are a million cows or a million
kangaroos.
Obviously, the article you read is erroneous and/or its author has a
huge grudge against Google.
Likewise, GWT allowing a browser to chew on its cud does not dictate
the efficiency of the data delivery system.
Mady
Jun 21, 2010, 2:40:48 PM6/21/10
to Google Web Toolkit
There are many GWT applications handling more then million users like
Gmail, Google Wave, Orkut etc... so can't believe that some one has
raise such concern.
On Jun 21, 1:25 pm, Jaroslav Záruba <jaroslav.zar...@gmail.com> wrote:
> What was such claim based on? It does sound weird to me.
> Client-side, which is where GWT operates mostly, does not care about how
> many users is accessing your website. By providing things like ClientBundle
> or code-splitting I think GWT helps your website handle loads of users
> better.
>
> On Sun, Jun 20, 2010 at 4:44 AM, manish kumar
> <manish.online2...@gmail.com>wrote:
> > .
Gmail, Google Wave, Orkut etc... so can't believe that some one has
raise such concern.
On Jun 21, 1:25 pm, Jaroslav Záruba <jaroslav.zar...@gmail.com> wrote:
> What was such claim based on? It does sound weird to me.
> Client-side, which is where GWT operates mostly, does not care about how
> many users is accessing your website. By providing things like ClientBundle
> or code-splitting I think GWT helps your website handle loads of users
> better.
>
> On Sun, Jun 20, 2010 at 4:44 AM, manish kumar
>
>
>
> > Hi, i have gone through many articles on web and found that GWT is not
> > good for an application that has million users access simultaniouly.
> > Is that really true? If not then what should i do make it accessible
> > by million users?Is that really tough job in GWT?
>
> > --
> > 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-we...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-web-tool...@googlegroups.com<google-web-toolkit%2Bunsubs cr...@googlegroups.com>
>
>
> > Hi, i have gone through many articles on web and found that GWT is not
> > good for an application that has million users access simultaniouly.
> > Is that really true? If not then what should i do make it accessible
> > by million users?Is that really tough job in GWT?
>
> > --
> > 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-we...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > .
Reply all
Reply to author
Forward
0 new messages