We can measure with yslow to see what we get. 50 ms I understand is
good and 200 to 300 ms approvable. Where I need to optimize is where
there are timeouts (where generating zip files) where responses are so
slow as taking seconds. I measured with yslow and an idea, for
optimization, is that we
Hey Niklas,
Maybe you could also come up with a simple caching strategy for your
rendered templates. Depending on the site, it might make content
updates easier later on.
Robert
On Fri, May 6, 2011 at 07:14, Niklas Rosencrantz nikla...@gmail.com wrote:
We can measure with yslow to see
Well said. :)
I thinking the other day neutrinos or muons might be a good way to
communicate on. :)
Brandon
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To
On Wed, May 4, 2011 at 5:10 PM, Brandon Donnelson
branflake2...@gmail.com wrote:
I got 40ms loading this http://demogwtcanvas.appspot.com/test.html
Brandon
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email
Its plain html no rendering. Eclipse uploaded. (mobile at moment)
On May 4, 2011 11:04 AM, Niklas Rosencrantz nikla...@gmail.com wrote:
On Wed, May 4, 2011 at 5:10 PM, Brandon Donnelson
branflake2...@gmail.com wrote:
I got 40ms loading this http://demogwtcanvas.appspot.com/test.html
Brandon
On Wed, May 4, 2011 at 6:30 PM, Brandon Donnelson
branflake2...@gmail.com wrote:
Its plain html no rendering. Eclipse uploaded. (mobile at moment)
On May 4, 2011 11:04 AM, Niklas Rosencrantz nikla...@gmail.com wrote:
On Wed, May 4, 2011 at 5:10 PM, Brandon Donnelson
branflake2...@gmail.com
Heres a demo I used to test GWT init and load a while back. Check chrome
developer tools network tab for trip times. When I set data to JDO through
RPC the trip is taking around 192ms to 255ms to insert to JDO and return to
tell me.
http://demogaeloadtest.appspot.com/
Of Brandon Wirtz
Sent: Sunday, May 01, 2011 2:39 AM
To: google-appengine@googlegroups.com
Subject: RE: [google-appengine] Is GAE expected to get faster in the
future?
Work on your code. Typically my requests are serving in 300ms . Of
course
there are a lot of factors
[mailto:google-appengine@googlegroups.com] On Behalf Of Brandon Wirtz
Sent: Sunday, May 01, 2011 2:39 AM
To: google-appengine@googlegroups.com
Subject: RE: [google-appengine] Is GAE expected to get faster in the
future?
Work on your code. Typically my requests are serving in 300ms . Of
course
(Google)
Sent: Monday, May 02, 2011 11:03 AM
To: Google App Engine
Subject: Re: [google-appengine] Re: Is GAE expected to get faster in the
future?
I'm not sure where you are getting those numbers from, but the network
routing looks like this:
User makes request - goes to a Google front end
@googlegroups.com [mailto:
google-appengine@googlegroups.com] *On Behalf Of *Ikai Lan (Google)
*Sent:* Monday, May 02, 2011 11:03 AM
*To:* Google App Engine
*Subject:* Re: [google-appengine] Re: Is GAE expected to get faster in the
future?
I'm not sure where you are getting those numbers from
Thanks for the interesting comments giving me some benchmarks to
compare with. I've now measured my app with yslow and some of my pages
load in about 200 ms while the slow ones take like 2 or 3 seconds. I
used to run this application on a dedicated physical server running
Linux + MySQL + JBoss
12 matches
Mail list logo
