Same problem today same time. I've created an issue: Issue 8788 <http://code.google.com/p/googleappengine/issues/detail?id=8788>: Every day around 9.00 AM Brussels time, huge drop in GAE performances
Please star it. Le mercredi 6 février 2013 13:59:05 UTC+1, Jacob G a écrit : > > Since Monday evening, I've seen terrible performance throughout the day on > GAE. Almost every request spawns a new instance, and the prior instance(s) > disappear without any information in the logs. Latency is terrible! > > Issue created here: > http://code.google.com/p/googleappengine/issues/detail?id=8781 > > Make sure you star it so it gets attention! > > On Wednesday, February 6, 2013 6:39:49 AM UTC-5, gafal wrote: >> >> This might help: At 9:00 AM, the GAE Daily quotas are reset. It might put >> GAE under a heavy load. >> >> here is a log of a cron (requestwhich does nothing (see code here under) >> execution duration. >> >> 1. >> 1. 2013-02-06 09:39:00.657 /cron/StayUp 200 6ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 2. >> 1. 2013-02-06 09:38:00.625 /cron/StayUp 200 76ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 3. >> 1. 2013-02-06 09:37:00.475 /cron/StayUp 200 8ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 4. >> 1. 2013-02-06 09:36:00.444 /cron/StayUp 200 7ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 5. >> 1. 2013-02-06 09:35:00.418 /cron/StayUp 200 9ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 6. >> 1. 2013-02-06 09:34:02.374 /cron/StayUp 200 1411ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 7. >> 1. 2013-02-06 09:33:00.869 /cron/StayUp 200 7ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 8. >> 1. 2013-02-06 09:32:00.789 /cron/StayUp 200 31ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 9. >> 1. 2013-02-06 09:31:00.701 /cron/StayUp 200 8ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 10. >> 1. 2013-02-06 09:30:00.629 /cron/StayUp 200 7ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 11. >> 1. 2013-02-06 09:29:00.561 /cron/StayUp 200 13ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 12. >> 1. 2013-02-06 09:28:02.473 /cron/StayUp 200 1432ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 13. >> 1. 2013-02-06 09:27:01.572 /cron/StayUp 200 525ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 14. >> 1. 2013-02-06 09:26:00.876 /cron/StayUp 200 11ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 15. >> 1. 2013-02-06 09:25:00.747 /cron/StayUp 200 534ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 16. >> 1. 2013-02-06 09:24:01.129 /cron/StayUp 200 82ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 17. >> 1. 2013-02-06 09:23:03.786 /cron/StayUp 200 2988ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 18. >> 1. 2013-02-06 09:22:00.555 /cron/StayUp 200 503ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 19. >> 1. 2013-02-06 09:21:01.022 /cron/StayUp 200 224ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 20. >> 1. 2013-02-06 09:20:01.810 /cron/StayUp 200 1274ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 21. >> 1. 2013-02-06 09:19:02.328 /cron/StayUp 200 1778ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 22. >> 1. 2013-02-06 09:18:00.498 /cron/StayUp 200 54ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 23. >> 1. 2013-02-06 09:17:04.781 /cron/StayUp 500 3733ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 2. W 2013-02-06 09:17:04.781 A problem was encountered with the >> process that handled this request, causing it to exit. This is likely >> to >> cause a new process to be used for the nex >> 24. >> 1. 2013-02-06 09:16:01.497 /cron/StayUp 200 1246ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 25. >> 1. 2013-02-06 09:15:02.913 /cron/StayUp 200 2100ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 26. >> 1. 2013-02-06 09:14:00.588 /cron/StayUp 200 44ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 27. >> 1. 2013-02-06 09:13:01.350 /cron/StayUp 200 375ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 28. >> 1. 2013-02-06 09:12:29.899 /cron/StayUp 200 89203ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 2. I 2013-02-06 09:11:23.884 javax.servlet.ServletContext log: >> Initializing Spring root WebApplicationContext >> 3. I 2013-02-06 09:12:29.895 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 requ >> 29. >> 1. 2013-02-06 09:10:00.559 /cron/StayUp 200 10ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 30. >> 1. 2013-02-06 09:09:00.335 /cron/StayUp 200 55ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 31. >> 1. 2013-02-06 09:08:01.068 /cron/StayUp 200 370ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 32. >> 1. 2013-02-06 09:07:00.547 /cron/StayUp 200 100ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 33. >> 1. 2013-02-06 09:06:00.059 /cron/StayUp 200 11ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 34. >> 1. 2013-02-06 09:05:01.017 /cron/StayUp 200 161ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 35. >> 1. 2013-02-06 09:04:00.693 /cron/StayUp 200 15ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 36. >> 1. 2013-02-06 09:03:00.600 /cron/StayUp 200 25ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 37. >> 1. 2013-02-06 09:02:00.558 /cron/StayUp 200 9ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 38. >> 1. 2013-02-06 09:01:00.338 /cron/StayUp 200 143ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 39. >> 1. 2013-02-06 09:00:01.092 /cron/StayUp 200 230ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 40. >> 1. 2013-02-06 08:59:00.819 /cron/StayUp 200 182ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 41. >> 1. 2013-02-06 08:58:00.553 /cron/StayUp 200 34ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 42. >> 1. 2013-02-06 08:57:01.346 /cron/StayUp 200 401ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 43. >> 1. 2013-02-06 08:56:00.868 /cron/StayUp 200 210ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 44. >> 1. 2013-02-06 08:55:00.561 /cron/StayUp 200 12ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 45. >> 1. 2013-02-06 08:54:00.454 /cron/StayUp 200 9ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 46. >> 1. 2013-02-06 08:53:00.331 /cron/StayUp 200 9ms 0kb AppEngine-Google; >> (+http://code.google.com/appengine) >> 47. >> 1. 2013-02-06 08:52:00.242 /cron/StayUp 200 12ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 48. >> 1. 2013-02-06 08:51:01.118 /cron/StayUp 200 70ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 49. >> 1. 2013-02-06 08:50:00.903 /cron/StayUp 200 223ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> 50. >> 1. 2013-02-06 08:49:00.592 /cron/StayUp 200 42ms 0kb >> AppEngine-Google; >> (+http://code.google.com/appengine) >> >> >> >> public class StayUp extends HttpServlet { >> >> /** >> * >> */ >> private static final long serialVersionUID = -3371245850830199827L; >> >> public void doGet(HttpServletRequest req, HttpServletResponse resp) >> throws ServletException, IOException { >> >> >> >> } >> >> Le mercredi 6 février 2013 12:27:59 UTC+1, Per a écrit : >>> >>> >>> While I haven't seen that problem, I'd love to learn more about it. Do >>> you have more information other than "it being slow"? Did you try running >>> appstats? Is it db-related, memcache, CPU slowness, or maybe even >>> session-related? Google may find out by looking at your app, but us others >>> cannot, and I'd love to hear what that actual issue is, in case we run into >>> something similar. >>> >>> >>> On Wednesday, February 6, 2013 9:12:40 AM UTC+1, gafal wrote: >>>> >>>> Happening again today 6th February. >>>> Can anyone at Google just care? It would really be appreciated... >>>> >>>> >>>> Le mardi 5 février 2013 09:18:55 UTC+1, gafal a écrit : >>>>> >>>>> I've been experiencing this for almost a week now. >>>>> >>>>> Requests take 10x longer than usual!! >>>>> >>>>> It seems to start around 9 and stop around 9:30... >>>>> >>>>> >>>>> my app id is myagendapro >>>>> Can anyone have a look? >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
