I'm getting cycled out at less than a minute as well, using openbd.
On Thu, Jun 3, 2010 at 4:07 PM, Tin tin.c...@gmail.com wrote:
Hi all:
I think every body who uses GAE should star this issue :
http://goo.gl/juDy
-- PLEASE HELP !!
Thank you very much ~
--
You received this message
I think the newer accounts are the ones having problems. On my account (much
older), same app doesn't cycle as much.
In theory, there is enough capacity such that as long as you get some
traffic every few hours, you should not be getting cycled out... - famous
last words.
On Fri, Jun 4, 2010 at
Spoke too soon.
I think if clients complain I'll just move them to a vps.
But, just thinking about managing separate VPS accounts for every client
gives me a headache.
Hopefully this gets fixed soon though, because I do love working on
appengine.
On Fri, Jun 4, 2010 at 12:19 AM, atomi
Folks, I had some evidence last year (
http://paulhammant.com/blog/appengines-blind-spot.html ) that it was a
second app-engine instance being started from my app and not the first
instance being taken down, and a new one started up.
Specifically, it seemed to me that second and subsequent
Hi all:
I think every body who uses GAE should star this issue : http://goo.gl/juDy
-- PLEASE HELP !!
Thank you very much ~
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To post to this group, send email to
My big wonder all along is why only some people get it and not
others. My restarts have always happened frequently - sometimes 1-2
restarts within the same page load. But, evidenced by my issue post,
most people don't have this problem. Did you change anything
recently?
Anyways, just more
This is quite an UGLY UGLY issue. GAEJ was working great till now.
May have to start looking for alternatives. Seeing restarts within a
few seconds to a few minutes of one another...
05-05 10:41PM 29.289 This request caused a new process to be started
for your application,
...
05-05 10:41PM
Another wicket user!
I'm down to about 2-3 seconds for the WicketFilter init(), which
includes the Application init(). Since I figure I'm only allowed
about 2-3 seconds, I realized that it was either give up Wicket or
give up JDO. So, I swapped out JDO for Objectify and couldn't be
happier.
I'm also still seeing this issue. I have an open ticket here:
http://code.google.com/p/googleappengine/issues/detail?id=2931 but
it's not getting much attention :)
Anyways, I've seen this as encouragement to make my startup time much
more efficient, so I guess that's a good thing :) My
Yes, I've done the same thing. In my case, the numbers about initialization
are these:
3 sec - gae (apparently some internal thing)
2 sec - presentation framework initialization (wicket in my case)
4 sec - 2 sec for pm factory creation + 2 sec for 2/3 queries I make
1 sec - wicket and maybe some
I'm also seeing my app being cycled too quickly.
- What is your application ID?
wicket-gae-template
- How do you know it is being cycled out? You'll need to insert some
code
that only gets called when the app cold starts.
startup is logged in a filter init() method; also logged in a static
I am experiencing the same problem. I am using Spring MVC. When is
the expected date for solution? I am waiting for solution for long. If
this problem persists, I have to switch to other platform.
On Mar 3, 6:41 pm, SRF srfar...@gmail.com wrote:
I'm also seeing my app being cycled too
Me too App ID ArachnoDB loading GData and its dependencies, happens
about every 2 minutes on average, I will add in a logger and follow up
but I can tell a load request from a normal request.
On Jan 15, 6:32 pm, Ikai Lan i...@google.com wrote:
Hey everybody,
We've been seeing more and more
Hi.. I apologize for reviving this post, but this problem is really
hitting me hard. I have an interactive fiction site
(www.friedfiction.com) that has been experiencing some terrible
response times over the past month. After investigating, it appears
that my app is cold starting almost every
Seems to be the case for me too, I've been noticing instance restarts
pretty often these last 2 or 3 days.
On 8 fév, 19:02, Ikai L (Google) ika...@google.com wrote:
Thanks for the info, Jake. Has anyone else experienced this? That is, has
anyone else noticed improvement which has since
Hey all,
Since Ikai's post on January 22nd, I haven't had much trouble with my
instance rebooting unexpectedly. However, today the problem has
returned. I'm getting instance restarts within a minute or two of
each other on a somewhat regular basis - sometimes even within a few
seconds of each
Thanks for the info, Jake. Has anyone else experienced this? That is, has
anyone else noticed improvement which has since degraded?
On Mon, Feb 8, 2010 at 9:10 AM, Jake jbrooko...@cast.org wrote:
Hey all,
Since Ikai's post on January 22nd, I haven't had much trouble with my
instance
I have only been experiencing this problem in the last few weeks
(after the 'fix' ?).
- What is your application ID?
salsa-amsterdam
- How do you know it is being cycled out? You'll need to insert some code
that only gets called when the app cold starts.
I am using a static AtomicBoolean to
I am having this problem for the last week or two after months of good
performance and very little recycling.
As my app start up time is around 15 seconds this is really hitting my
user experience in a negative way.
On Jan 16, 12:32 am, Ikai Lan i...@google.com wrote:
Hey everybody,
We've been
Ikai,
Me too I can report an improved response time and no datastote timeout
exceptions the past couple of days. I have no measurements so far, but
the improvement is noticeable. I'll certainly keep watching and let
you know of any relevant issues.
Thanks!
Jorge Gonzalez
On Jan 22, 9:10 pm,
Hey everybody,
I just wanted to give an update about this issue. We've changed resource
allocation for our Java developers, which should result in much less app
evictions. Some of you may have already noticed an improvement. I've already
received several encouraging messages from developers who
Ikai,
Great news. I can report that I'm seeing FAR fewer cold starts
today. So thank you!
Would still love to see this implemented:
http://code.google.com/p/googleappengine/issues/detail?id=2456
cheers
-- James
--
You received this message because you are subscribed to the Google Groups
The dollar cost of apps being initialized more than they need to has
always concerned me though.
This is an important observation. Keeping our apps loaded with cron or
other hacks is discouraged, yet we are billed for far more CPU usage
if we allow appengine to unload/reload our apps every few
I suspect that Google can't price up the RAM in use by node.
Or at least given
http://gregluck.com/blog/archives/2009/06/the-limitations-of-google-app-engine/
they can't do fine grained billing based on stack/heap usage.
I think they'd need to be able to do that before allowing us to keep
I would be happy if they could page the heap of a quiet app to disk
instead in re-initialising. To read even 100MB from disc would take
less than a second... maybe another to send it across the network. A
delay on that scale wouldn't worry me.
On 19 Jan 2010, at 00:20, Paul Hammant
Mine happens at pretty random rates too
- What is your application ID?
footbattle
- How do you know it is being cycled out? You'll need to insert some code
that only gets called when the app cold starts.
Random Request was aborted after waiting too long to attempt to
service your request.
- What is your application ID?
wcondominios
- How do you know it is being cycled out? You'll need to insert some code
that only gets called when the app cold starts.
I just see incredibly long response times. This, for instance:
#
01-16 04:29AM 02.107 / 302 4752ms 6718cpu_ms 126api_cpu_ms
27 matches
Mail list logo
