Tim, Datastore latencies do coincide with application startup times, but they are not the cause. The root cause is usually the underlying I/O. We're working on long term solutions for these issues.
Neal, we'll be shipping "Always On" as a billing enabled feature in 1.4.0. You'll definitely want to make use of this in your application to prevent this from happening. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Mon, Nov 29, 2010 at 10:10 PM, Tim Hoffman <zutes...@gmail.com> wrote: > Yep > > thats exactly what is happening. The site is taking too long to > start, > imports seem to be affected by a range of appengine slow downs > (i firmly believe elevated datastore latencies coincide with extended > startup times). > > Warm starts my be useful for you as well as the soon to be available > always on instances. > > Some other strategies you can adopt to shrink startup times is trying > to defer > some of your imports until you need to use the stuff. > > We have fast paths to retrieve relatively static content from > memcache > without even starting up a full stack. (ie only importing core api's > from appengine) > > This can usually get us an instance cold started and serving the front > page in less 200ms > > understanding how you app starts and Tuning, tuning tuning the > startup, I feel is really important for a good > user experience. > > Rgds > > > Tim > > On Nov 30, 1:49 pm, NealWalters <nealwalt...@nealwalters.com> wrote: > > I've read several other posts on this error, but they seem to be > > inconclusive and several months old. > > We are a startup, so our site is not used frequently, but when used, > > it is often someone we are trying to impress, > > so we MUST have some solution for this issue if we indeed continue to > > use GAE. > > > > Since the trace is showing the errors on "import" statements, I'm > > thinking this is the case where the system got "cold" and must "warm > > up"? > > > > WebSite ishttp://Olexe.com. > > > > From my logs, this happened at least four times today on our home > > page: > > > > E-Level Message: > > <class 'google.appengine.runtime.DeadlineExceededError'>: > > Traceback (most recent call last): > > File "/base/data/home/apps/olexeprod/1.346221763725918442/main.py", > > line 296, in <module> > > from web.webServices import Subscribers > > File "/base/data/home/apps/olexeprod/1.346221763725918442/web/ > > webServices.py", line 15, in <module> > > import gnosis.xml.pickle > > File "/base/data/home/apps/olexeprod/1.346221763725918442/gnosis/xml/ > > pickle/__init__.py", line 6, in <module> > > from gnosis.xml.pickle._pickle import \ > > File "/base/data/home/apps/olexeprod/1.346221763725918442/gnosis/xml/ > > pickle/_pickle.py", line 5, in <module> > > """ > > I-Level Message: > > This request caused a new process to be started for your application, > > and thus caused your application code to be loaded for the first time. > > This request may thus take longer and use more CPU than a typical > > request for your application. > > > > Please advise, > > Thanks, > > Neal Walters > > -- > 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-appeng...@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com<google-appengine%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- 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-appeng...@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
