Brandon, Test on Master/Slave.
Not keeping point that my code is perfect I keep point that GEA LOAD behavior is RANDOM/UNPREDICTED - once it load faster (5s) once it not loads since DeadlineExceed (70s) - it not enough for production system. Problem start from last weeks. I will do some imports tracing and found what imports has the major impact but problem is that its load RANDOM once faster once longer - I do some downgrade one module but still GAE works worser than before but should work faster since added very fast caching and optimizations. Planning to do HRD to see if it has any impact on customer experience/ availabity. See how random it is (first load time if from module start and second for the single module). Shows time only above second - both requests has same input variance is from 17s, 30s till deadline - it is NOT STABLE: 2012-01-17 14:16:07.807 ImportLogger 1.03 1.02 - frontend.web.handlers - frontend.web.handlers.common:17. D 2012-01-17 14:16:09.310 ImportLogger 2.53 1.50 - google - frontend.web.handlers.common:28. D 2012-01-17 14:16:10.164 ImportLogger 3.38 0.53 - frontend.web.cookie - frontend.web.handlers.common:45. D 2012-01-17 14:16:11.118 ImportLogger 4.34 0.95 - frontend.web - frontend.web.handlers.common:47. D 2012-01-17 14:16:12.106 ImportLogger 5.32 0.93 - frontend.web.authentication - frontend.web.handlers.common:52. D 2012-01-17 14:16:12.239 ImportLogger 6.66 6.66 - common handler - __main__:13. D 2012-01-17 14:16:18.552 ImportLogger 12.97 6.31 - frontend.restaurant - __main__:29. D 2012-01-17 14:16:19.886 ImportLogger 1.23 1.23 - cssutils - css_inliner:8. D 2012-01-17 14:16:19.924 ImportLogger 1.30 1.28 - css_inliner - frontend.ordering.messages:24. D 2012-01-17 14:16:22.118 ImportLogger 3.50 2.13 - utilities.time - frontend.ordering.messages:39. D 2012-01-17 14:16:22.579 ImportLogger 3.97 3.96 - frontend.ordering - frontend.ordering.processing:22. D 2012-01-17 14:16:22.642 ImportLogger 17.06 4.04 - frontend.ordering - __main__:35. 2012-01-17 14:15:41.905 ImportLogger 0.95 0.61 - frontend.ordering.order - __main__:33. D 2012-01-17 14:15:59.633 ImportLogger 17.32 17.32 - cssutils - css_inliner:8. D 2012-01-17 14:16:03.322 ImportLogger 21.01 3.69 - BeautifulSoup - css_inliner:13. D 2012-01-17 14:16:04.559 ImportLogger 22.25 1.24 - pynliner.soupselect - css_inliner:17. D 2012-01-17 14:16:04.559 ImportLogger 22.51 22.37 - css_inliner - frontend.ordering.messages:24. D 2012-01-17 14:16:06.902 ImportLogger 24.85 2.34 - messaging.sms.smsapipl - frontend.ordering.messages:27. D 2012-01-17 14:16:07.636 ImportLogger 25.59 0.73 - link_shortener - frontend.ordering.messages:29. D 2012-01-17 14:16:08.990 ImportLogger 26.94 0.64 - globals - frontend.ordering.messages:54. D 2012-01-17 14:16:08.990 ImportLogger 27.02 27.01 - frontend.ordering - frontend.ordering.processing:22. D 2012-01-17 14:16:10.166 ImportLogger 28.20 0.85 - frontend.ordering.order_state_controller - frontend.ordering.processing:26. D 2012-01-17 14:16:12.010 ImportLogger 30.04 1.84 - frontend.billing - frontend.ordering.processing:30. D 2012-01-17 14:16:12.010 ImportLogger 31.06 30.10 - frontend.ordering - __main__:35. On Jan 17, 10:50 am, "Brandon Wirtz" <[email protected]> wrote: > You keep pointing to reasons you believe it isn't your code, and why we are > wrong, but you aren't trying the things we point out. If your time out are > at 70 seconds you are doing something wrong, it shouldn't take that long to > start up. EVER. > > Also you are on M/S which has its own rules. Jump in to the modern world and > run on HR with the rest of us happy shiny people, rather than running on the > unsupported, failed experiment that M/S is. > > > > > > > > -----Original Message----- > From: [email protected] > > [mailto:[email protected]] On Behalf Of Cezary Wagner > Sent: Tuesday, January 17, 2012 1:43 AM > To: Google App Engine > Subject: [google-appengine] Re: Why are several production issues related to > DeadlineExceededErrors being ignored? > > Kenneth, > > The timeouts could not be 10s or 15s - since DeadlineExceededErrors occurs > in my logs is about 60s - I think that 10s or 15s is myths or wrong > implementation since what is sense to give 60s if it should start in 15s??? > > Common timeouts are: 64608ms, 70806ms, 63093ms, 64499ms, ... > > On Jan 17, 9:10 am, Kenneth <[email protected]> wrote: > > Wow, sorry to hear that. Is it java or python? I've been on hrd now > > for about a month. I have the sliders set to el cheapo mode and > > haven't had any timeouts at all. > > > My understanding is the startup timeout is 10 seconds. The total > > request timeout is 60 seconds. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
