...@googlegroups.com] On Behalf Of Jake
Sent: Friday, March 19, 2010 8:56 AM
To: Google App Engine for Java
Subject: [appengine-java] Re: App instance recycling and response times - is
there solution?
Hey James,
Also thanks for the clarification. It hadn't occurred to me that what
On Mon, Mar 22, 2010 at 7:21 AM, Guillermo Schwarz
guillermo.schw...@gmail.com wrote:
In order to load the app, a kind of core file must be read from disk
in order to represent the app state in RAM. That process takes too
long (used to be up to 3 secs, now it is up to 12 seconds AFAIK)
It makes sense because web server apps are staless anyway, so what
would be the point of storing the state?
The only problem would be that Spring apps take so long to start up.
Anyway, I think the problem is something else, because when loaded the
application is very fast and I'm not using Spring
As a followup, today (3/17) from 1-3PM PST I received several
instances of Request
was aborted after waiting too long to attempt to service your request. This
is on my app w/ zero users, just 3 requests/minute of a blank page as a test
load.
On Thu, Mar 11, 2010 at 1:50 PM, Don Schwarz
This is NOT just a problem with Spring -- stop talking like
optimization is going to fix things. It takes too much time for a
naked servlet to load (i.e; 5-10 seconds). The only jars that I have
are for JPA.
On Jan 12, 8:32 pm, Jeff Schnitzer j...@infohazard.org wrote:
I've been thinking about
I setup some pings of my add a few minutes ago, and I'm still seeing
recycling :(
My ping setup can't go lower than 60s intervals, so I have two running
concurrently. Here's a sample of 20 log entries over 10 minutes,
with . Three recyclings occur, and they happen less than 10s after a
previous
Can you respond privately with your app id?
On Thu, Mar 11, 2010 at 10:10 AM, James jamesk...@gmail.com wrote:
I setup some pings of my add a few minutes ago, and I'm still seeing
recycling :(
My ping setup can't go lower than 60s intervals, so I have two running
concurrently. Here's a
If you are experiencing failed requests on your long-running /
requests, consider performing some kind of pre-warming procedure of
your own... If you are getting timeout errors, Ping a do-nothing url,
and wait for it to return before running the big job. If it's a big
job, users should expect to
治本只能等GAE的升级了，这样确实只能保证你的应用不会因为两分钟没有请求被关闭！
不知道GAE收费版本是不是没有这个问题
2010/1/13 yjun hu itswa...@gmail.com
治标不治本
On Wed, Jan 13, 2010 at 1:24 PM, 杨浩 skzr@gmail.com wrote:
create a cron:every one minutes to run for keep your app online in the
GAE!
I try it,and it is work very good!
--
dream
Jeff,
in one point i disagree.
In a high available einvironment you would have a cluster of load balanced
application servers and you would deploy new versions of your app in turn,
one at a time.
So if one instance is down the other(s) will continue serving your users
(though it might require
On Thu, Jan 14, 2010 at 12:59 PM, Stephan Hartmann hartm...@metamesh.de wrote:
Jeff,
in one point i disagree.
In a high available einvironment you would have a cluster of load balanced
application servers and you would deploy new versions of your app in turn,
one at a time.
So if one
I've tried this, but after 1 day, GAE recycled my instance every 40 seconds.
Then I used task queue to request my site per 30 seconds, but GAE
started to recycle every 20 seconds.
So I don't think it's a good way.
2010/1/13 杨浩 skzr@gmail.com:
create a cron:every one minutes to run for keep
I don't have time to go into details, so this is a 10,000 ft view, but
perhaps you could potentially extend the base spring context listener
to work with the distributed cache (or some other mechanism between
web apps) which keeps an instance of springs context so that it
doesn't have to be
I asked same question on Stack Overflow (http://stackoverflow.com/
questions/2051036/google-app-engine-application-instance-recycling-and-
response-times).
So far proposed solutions (in SO thread and found on other websites)
do not satisfy me. Creating cron or any other kind of periodic HTTP
Make sure you are using offline precompilation. We are always working on
optimizations to decrease the latency of loading requests, but here are some
other tips:
http://googleappengine.blogspot.com/2009/12/request-performance-in-java.html
On Tue, Jan 12, 2010 at 3:01 PM, Locke
I've been thinking about this issue a little. It's not quite as
straightforward as just keeping an instance warm. Even if you have an
app that gets multiple hits per second, there will still be cold
starts:
* When a new instance comes online to serve more demand.
* When you redeploy a version
This is a tragedy of the commons. It may in fact work for you right
now, and will continue to work... until it doesn't. It will stop
working when enough people figure it out and millions of zombie
applications push the working applications out of memory. Or Google
pulls the plug on this
治标不治本
On Wed, Jan 13, 2010 at 1:24 PM, 杨浩 skzr@gmail.com wrote:
create a cron:every one minutes to run for keep your app online in the GAE!
I try it,and it is work very good!
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
18 matches
Mail list logo
