Looks like the limit has been raised! Haven't tested yet what is the higher
limit but I have an instance with almost 19000 requests so it has been more
than doubled, at least. Good news!
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java
Thank you! This is very good news, and gives motivation to optimize the code
to run fast :)
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Possibly - with a multithreaded Java runtime this really might not make
sense anymore. I'll look into it.
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: http://www.reddit.com/r/appengine
On Thu,
Received confirmation that this limit is going to be raised. I don't have an
ETA for this.
Ikai Lan
Developer Programs Engineer, Google App Engine
Blog: http://googleappengine.blogspot.com
Twitter: http://twitter.com/app_engine
Reddit: http://www.reddit.com/r/appengine
On Fri, Jul 8, 2011 at
Thank you! I didn't know about this and tried to search (also on these
forums).
In my production app I get instance restart every 6 minutes, that's 10 times
per hour! I think I should de-optimize my code to run slower to make GAE
to use more instances with my current load, so my users
This is an interesting issue. Hopefully someone at Google has considered
this when making changes to the scheduler.
Instance death after 9k requests is a known behavior of GAE (well, known
if you read these forums - I don't think there is any official
documentation). As a wild guess on my part,
Hi,
I've been testing possible memory leak in my app using JDO. I created a
small app with two servlets, the other servlet creating one small JDO entity
and the other servlet creating an entity with Objectify. Running the test
with JMeter I've realised the memory usage grows quite a bit when
