Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
I'm experiencing this problem as well and can not demo my app. app id: gobandpass For me each request is starting a new instance thus causing long response times. I am in development and therefore the only person on the app. So I can clearly see for each client request a new instance is being started. Performance settings are (and always have been) automatic, automatic for both instance and latency which always seemed to work fine until now. Note, timing wise, I deployed an app on 12/13 and everything tested out fine. Then on 1/8 I deployed again and now have this problem. In between these dates I was working locally and therefore would not notice exactly when this problem cropped up. Somewhere between 12/3 and 1/8. On Thursday, December 27, 2012 1:18:47 PM UTC-8, Saket Kumar wrote: Hi Carl, Can you let me know your app-id? Regards, Saket On Thursday, 27 December 2012 20:01:30 UTC+1, Carl Schroeder wrote: I am still seeing java instances decomissioned after sub minute quiet periods. Given that it takes 20-30 seconds to spin one java instance up, you should probably leave them alive for a bit longer than a few seconds. Otherwise, for low traffic profiles, page loads for GAE java can take up to 30 seconds. God help us if the scheduler thinks I need 2 new instances spun up in series rather than parallel. FYI, people don't wait around for a minute for pages to load. They use other services. Once again, due to unannounced pathological behavior of the instancing on GAE, we are wasting our time re-implementing our java infrastructure on AWS. At least, I hope it is a waste of our time... On Tuesday, December 25, 2012 4:00:26 PM UTC-8, Francois Masurel wrote: Hi Saket, Thanx for investigating the problem. Things seems to have improved significantly these last few days. On our Neustar reports, for an average page loading, we can see that we went from 6.65shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/16) to 8.94s (12/18) and back to 2.57shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/23). I can confirm that we don't see as much instance warm ups in our logs as we were used before, we went from every 3-4 minutes to 20-25 minutes. I definitely think things have changed on Google side as we haven't changed anything on our side. But some strange things are still going on at the moment (12/26 0:52 UTC+1) as a dynamic instance has been up for more than 4 hours but has served only one request (cf. screenshot below). Thanx again Saket for your help. François https://lh6.googleusercontent.com/-ARDAA2Yu-NY/UNo-Bgn9SpI/yN8/NNC4QLzi93g/s1600/Instances+-+VinoCities+-+Google+Chrome.jpg On Monday, December 24, 2012 11:54:48 PM UTC+1, Saket Kumar wrote: Hi Francois, Are you still facing this issue? I did a small test for your application and didn't find anything too bad from scheduler's perspective. I'm trying to understand if it was a temporary glitch that was causing the issue or something is wrong with scheduler's algorithm. Or if scheduler doesn't spin instances properly if QPS is low. Here is series of events- a.) Single resident was serving for 1 day, 03:26:37 minutes, serving 9600 request b.) After serving 96 requests with raised QPS, new instance was created. c.) QPS lowered and the new instance was allowed to die. d.) Again the QPS was increased and new instance was created. Both instances were handling requests at this point. e.) QPS lowered again, newly formed instance dies and older instance starts serving 100% of the requests. - Saket On Saturday, 22 December 2012 12:18:00 UTC+1, Francois Masurel wrote: Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All,
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
I am still seeing java instances decomissioned after sub minute quiet periods. Given that it takes 20-30 seconds to spin one java instance up, you should probably leave them alive for a bit longer than a few seconds. Otherwise, for low traffic profiles, page loads for GAE java can take up to 30 seconds. God help us if the scheduler thinks I need 2 new instances spun up in series rather than parallel. FYI, people don't wait around for a minute for pages to load. They use other services. Once again, due to unannounced pathological behavior of the instancing on GAE, we are wasting our time re-implementing our java infrastructure on AWS. At least, I hope it is a waste of our time... On Tuesday, December 25, 2012 4:00:26 PM UTC-8, Francois Masurel wrote: Hi Saket, Thanx for investigating the problem. Things seems to have improved significantly these last few days. On our Neustar reports, for an average page loading, we can see that we went from 6.65shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/16) to 8.94s (12/18) and back to 2.57shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/23). I can confirm that we don't see as much instance warm ups in our logs as we were used before, we went from every 3-4 minutes to 20-25 minutes. I definitely think things have changed on Google side as we haven't changed anything on our side. But some strange things are still going on at the moment (12/26 0:52 UTC+1) as a dynamic instance has been up for more than 4 hours but has served only one request (cf. screenshot below). Thanx again Saket for your help. François https://lh6.googleusercontent.com/-ARDAA2Yu-NY/UNo-Bgn9SpI/yN8/NNC4QLzi93g/s1600/Instances+-+VinoCities+-+Google+Chrome.jpg On Monday, December 24, 2012 11:54:48 PM UTC+1, Saket Kumar wrote: Hi Francois, Are you still facing this issue? I did a small test for your application and didn't find anything too bad from scheduler's perspective. I'm trying to understand if it was a temporary glitch that was causing the issue or something is wrong with scheduler's algorithm. Or if scheduler doesn't spin instances properly if QPS is low. Here is series of events- a.) Single resident was serving for 1 day, 03:26:37 minutes, serving 9600 request b.) After serving 96 requests with raised QPS, new instance was created. c.) QPS lowered and the new instance was allowed to die. d.) Again the QPS was increased and new instance was created. Both instances were handling requests at this point. e.) QPS lowered again, newly formed instance dies and older instance starts serving 100% of the requests. - Saket On Saturday, 22 December 2012 12:18:00 UTC+1, Francois Masurel wrote: Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks, Christina On Fri, Dec 21, 2012 at 8:39 AM, Carl Schroeder schroede...@gmail.comwrote: I've been sacrificing unicorns to dark powers...clearly I have been doing it wrong. That probably explains some unusual behavior in other parts of my app. AFK pentagrams. :( On Thursday, December 20, 2012 7:51:35 PM UTC-8, Cesium wrote: Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that I sprinkled rainbow Skittles across the floor to attract the unicorns. They're back! David -- You received this message because you are
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Also FYI, this whole issue could be resolved if you would stop sending user facing requests to cold uninitialized instances in java GAE. Handling user requests in ways that you know will cause 20+ second response times is pathological. All new development for us on GAE is blocked until this issue can be resolved. On Thursday, December 27, 2012 11:01:30 AM UTC-8, Carl Schroeder wrote: I am still seeing java instances decomissioned after sub minute quiet periods. Given that it takes 20-30 seconds to spin one java instance up, you should probably leave them alive for a bit longer than a few seconds. Otherwise, for low traffic profiles, page loads for GAE java can take up to 30 seconds. God help us if the scheduler thinks I need 2 new instances spun up in series rather than parallel. FYI, people don't wait around for a minute for pages to load. They use other services. Once again, due to unannounced pathological behavior of the instancing on GAE, we are wasting our time re-implementing our java infrastructure on AWS. At least, I hope it is a waste of our time... On Tuesday, December 25, 2012 4:00:26 PM UTC-8, Francois Masurel wrote: Hi Saket, Thanx for investigating the problem. Things seems to have improved significantly these last few days. On our Neustar reports, for an average page loading, we can see that we went from 6.65shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/16) to 8.94s (12/18) and back to 2.57shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/23). I can confirm that we don't see as much instance warm ups in our logs as we were used before, we went from every 3-4 minutes to 20-25 minutes. I definitely think things have changed on Google side as we haven't changed anything on our side. But some strange things are still going on at the moment (12/26 0:52 UTC+1) as a dynamic instance has been up for more than 4 hours but has served only one request (cf. screenshot below). Thanx again Saket for your help. François https://lh6.googleusercontent.com/-ARDAA2Yu-NY/UNo-Bgn9SpI/yN8/NNC4QLzi93g/s1600/Instances+-+VinoCities+-+Google+Chrome.jpg On Monday, December 24, 2012 11:54:48 PM UTC+1, Saket Kumar wrote: Hi Francois, Are you still facing this issue? I did a small test for your application and didn't find anything too bad from scheduler's perspective. I'm trying to understand if it was a temporary glitch that was causing the issue or something is wrong with scheduler's algorithm. Or if scheduler doesn't spin instances properly if QPS is low. Here is series of events- a.) Single resident was serving for 1 day, 03:26:37 minutes, serving 9600 request b.) After serving 96 requests with raised QPS, new instance was created. c.) QPS lowered and the new instance was allowed to die. d.) Again the QPS was increased and new instance was created. Both instances were handling requests at this point. e.) QPS lowered again, newly formed instance dies and older instance starts serving 100% of the requests. - Saket On Saturday, 22 December 2012 12:18:00 UTC+1, Francois Masurel wrote: Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks, Christina On Fri, Dec 21, 2012 at 8:39 AM, Carl Schroeder schroede...@gmail.com wrote: I've been sacrificing unicorns to dark powers...clearly I have been doing it wrong. That probably explains some unusual behavior in other parts of my app. AFK pentagrams. :( On Thursday, December 20, 2012 7:51:35 PM UTC-8,
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
FYI, my app is cruising along just fine with one instance that has been alive for 2 days. I feel your pain, brother. David On Thursday, December 27, 2012 12:12:27 PM UTC-7, Carl Schroeder wrote: Also FYI, this whole issue could be resolved if you would stop sending user facing requests to cold uninitialized instances in java GAE. Handling user requests in ways that you know will cause 20+ second response times is pathological. All new development for us on GAE is blocked until this issue can be resolved. On Thursday, December 27, 2012 11:01:30 AM UTC-8, Carl Schroeder wrote: I am still seeing java instances decomissioned after sub minute quiet periods. Given that it takes 20-30 seconds to spin one java instance up, you should probably leave them alive for a bit longer than a few seconds. Otherwise, for low traffic profiles, page loads for GAE java can take up to 30 seconds. God help us if the scheduler thinks I need 2 new instances spun up in series rather than parallel. FYI, people don't wait around for a minute for pages to load. They use other services. Once again, due to unannounced pathological behavior of the instancing on GAE, we are wasting our time re-implementing our java infrastructure on AWS. At least, I hope it is a waste of our time... On Tuesday, December 25, 2012 4:00:26 PM UTC-8, Francois Masurel wrote: Hi Saket, Thanx for investigating the problem. Things seems to have improved significantly these last few days. On our Neustar reports, for an average page loading, we can see that we went from 6.65shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/16) to 8.94s (12/18) and back to 2.57shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/23). I can confirm that we don't see as much instance warm ups in our logs as we were used before, we went from every 3-4 minutes to 20-25 minutes. I definitely think things have changed on Google side as we haven't changed anything on our side. But some strange things are still going on at the moment (12/26 0:52 UTC+1) as a dynamic instance has been up for more than 4 hours but has served only one request (cf. screenshot below). Thanx again Saket for your help. François https://lh6.googleusercontent.com/-ARDAA2Yu-NY/UNo-Bgn9SpI/yN8/NNC4QLzi93g/s1600/Instances+-+VinoCities+-+Google+Chrome.jpg On Monday, December 24, 2012 11:54:48 PM UTC+1, Saket Kumar wrote: Hi Francois, Are you still facing this issue? I did a small test for your application and didn't find anything too bad from scheduler's perspective. I'm trying to understand if it was a temporary glitch that was causing the issue or something is wrong with scheduler's algorithm. Or if scheduler doesn't spin instances properly if QPS is low. Here is series of events- a.) Single resident was serving for 1 day, 03:26:37 minutes, serving 9600 request b.) After serving 96 requests with raised QPS, new instance was created. c.) QPS lowered and the new instance was allowed to die. d.) Again the QPS was increased and new instance was created. Both instances were handling requests at this point. e.) QPS lowered again, newly formed instance dies and older instance starts serving 100% of the requests. - Saket On Saturday, 22 December 2012 12:18:00 UTC+1, Francois Masurel wrote: Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks, Christina On Fri, Dec 21, 2012 at 8:39 AM, Carl Schroeder schroede...@gmail.com wrote: I've been sacrificing
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Someone is not sharing their unicorns. :( On Thursday, December 27, 2012 11:32:01 AM UTC-8, Cesium wrote: FYI, my app is cruising along just fine with one instance that has been alive for 2 days. I feel your pain, brother. David On Thursday, December 27, 2012 12:12:27 PM UTC-7, Carl Schroeder wrote: Also FYI, this whole issue could be resolved if you would stop sending user facing requests to cold uninitialized instances in java GAE. Handling user requests in ways that you know will cause 20+ second response times is pathological. All new development for us on GAE is blocked until this issue can be resolved. On Thursday, December 27, 2012 11:01:30 AM UTC-8, Carl Schroeder wrote: I am still seeing java instances decomissioned after sub minute quiet periods. Given that it takes 20-30 seconds to spin one java instance up, you should probably leave them alive for a bit longer than a few seconds. Otherwise, for low traffic profiles, page loads for GAE java can take up to 30 seconds. God help us if the scheduler thinks I need 2 new instances spun up in series rather than parallel. FYI, people don't wait around for a minute for pages to load. They use other services. Once again, due to unannounced pathological behavior of the instancing on GAE, we are wasting our time re-implementing our java infrastructure on AWS. At least, I hope it is a waste of our time... On Tuesday, December 25, 2012 4:00:26 PM UTC-8, Francois Masurel wrote: Hi Saket, Thanx for investigating the problem. Things seems to have improved significantly these last few days. On our Neustar reports, for an average page loading, we can see that we went from 6.65shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/16) to 8.94s (12/18) and back to 2.57shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/23). I can confirm that we don't see as much instance warm ups in our logs as we were used before, we went from every 3-4 minutes to 20-25 minutes. I definitely think things have changed on Google side as we haven't changed anything on our side. But some strange things are still going on at the moment (12/26 0:52 UTC+1) as a dynamic instance has been up for more than 4 hours but has served only one request (cf. screenshot below). Thanx again Saket for your help. François https://lh6.googleusercontent.com/-ARDAA2Yu-NY/UNo-Bgn9SpI/yN8/NNC4QLzi93g/s1600/Instances+-+VinoCities+-+Google+Chrome.jpg On Monday, December 24, 2012 11:54:48 PM UTC+1, Saket Kumar wrote: Hi Francois, Are you still facing this issue? I did a small test for your application and didn't find anything too bad from scheduler's perspective. I'm trying to understand if it was a temporary glitch that was causing the issue or something is wrong with scheduler's algorithm. Or if scheduler doesn't spin instances properly if QPS is low. Here is series of events- a.) Single resident was serving for 1 day, 03:26:37 minutes, serving 9600 request b.) After serving 96 requests with raised QPS, new instance was created. c.) QPS lowered and the new instance was allowed to die. d.) Again the QPS was increased and new instance was created. Both instances were handling requests at this point. e.) QPS lowered again, newly formed instance dies and older instance starts serving 100% of the requests. - Saket On Saturday, 22 December 2012 12:18:00 UTC+1, Francois Masurel wrote: Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks,
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Hi Carl, Can you let me know your app-id? Regards, Saket On Thursday, 27 December 2012 20:01:30 UTC+1, Carl Schroeder wrote: I am still seeing java instances decomissioned after sub minute quiet periods. Given that it takes 20-30 seconds to spin one java instance up, you should probably leave them alive for a bit longer than a few seconds. Otherwise, for low traffic profiles, page loads for GAE java can take up to 30 seconds. God help us if the scheduler thinks I need 2 new instances spun up in series rather than parallel. FYI, people don't wait around for a minute for pages to load. They use other services. Once again, due to unannounced pathological behavior of the instancing on GAE, we are wasting our time re-implementing our java infrastructure on AWS. At least, I hope it is a waste of our time... On Tuesday, December 25, 2012 4:00:26 PM UTC-8, Francois Masurel wrote: Hi Saket, Thanx for investigating the problem. Things seems to have improved significantly these last few days. On our Neustar reports, for an average page loading, we can see that we went from 6.65shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/16) to 8.94s (12/18) and back to 2.57shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/23). I can confirm that we don't see as much instance warm ups in our logs as we were used before, we went from every 3-4 minutes to 20-25 minutes. I definitely think things have changed on Google side as we haven't changed anything on our side. But some strange things are still going on at the moment (12/26 0:52 UTC+1) as a dynamic instance has been up for more than 4 hours but has served only one request (cf. screenshot below). Thanx again Saket for your help. François https://lh6.googleusercontent.com/-ARDAA2Yu-NY/UNo-Bgn9SpI/yN8/NNC4QLzi93g/s1600/Instances+-+VinoCities+-+Google+Chrome.jpg On Monday, December 24, 2012 11:54:48 PM UTC+1, Saket Kumar wrote: Hi Francois, Are you still facing this issue? I did a small test for your application and didn't find anything too bad from scheduler's perspective. I'm trying to understand if it was a temporary glitch that was causing the issue or something is wrong with scheduler's algorithm. Or if scheduler doesn't spin instances properly if QPS is low. Here is series of events- a.) Single resident was serving for 1 day, 03:26:37 minutes, serving 9600 request b.) After serving 96 requests with raised QPS, new instance was created. c.) QPS lowered and the new instance was allowed to die. d.) Again the QPS was increased and new instance was created. Both instances were handling requests at this point. e.) QPS lowered again, newly formed instance dies and older instance starts serving 100% of the requests. - Saket On Saturday, 22 December 2012 12:18:00 UTC+1, Francois Masurel wrote: Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks, Christina On Fri, Dec 21, 2012 at 8:39 AM, Carl Schroeder schroede...@gmail.com wrote: I've been sacrificing unicorns to dark powers...clearly I have been doing it wrong. That probably explains some unusual behavior in other parts of my app. AFK pentagrams. :( On Thursday, December 20, 2012 7:51:35 PM UTC-8, Cesium wrote: Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Saket, Didn't we already discuss this a couple of days ago? David On Dec 24, 2012 5:20 PM, Saket Kumar sak...@google.com wrote: Hi Cesium, Can you share your app-id as well? Thanks! Saket On Monday, 17 December 2012 16:32:40 UTC+1, Cesium wrote: On Dec 16, something changed. Now, instances do not survive more than a couple minutes of inactivity (no incoming requests). Thus, low traffic applications see long latency since a new instance is created for the request. This is disastrous for my application (and customers). Can someone please help? Thanks, David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/LOXI1o2m_dgJ. To post to this group, send email to google-appengine@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. -- 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-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
These are my previous posts which got approved now. On Tuesday, 25 December 2012 17:37:55 UTC+1, Cesium wrote: Saket, Didn't we already discuss this a couple of days ago? David On Dec 24, 2012 5:20 PM, Saket Kumar sak...@google.com javascript: wrote: Hi Cesium, Can you share your app-id as well? Thanks! Saket On Monday, 17 December 2012 16:32:40 UTC+1, Cesium wrote: On Dec 16, something changed. Now, instances do not survive more than a couple minutes of inactivity (no incoming requests). Thus, low traffic applications see long latency since a new instance is created for the request. This is disastrous for my application (and customers). Can someone please help? Thanks, David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/LOXI1o2m_dgJ. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. 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 view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/KvDWXY27JtoJ. To post to this group, send email to google-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Hi Saket, Thanx for investigating the problem. Things seems to have improved significantly these last few days. On our Neustar reports, for an average page loading, we can see that we went from 6.65shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/16) to 8.94s (12/18) and back to 2.57shttps://monitor.wpm.neustar.biz/reports/graph_log/#/?monitorIds=8bc3b100-b372-11e1-a749-9848e1660ab3timeRange=last_24_hoursfunctionType=loadtimegraphType=line_chartview=loadtime (12/23). I can confirm that we don't see as much instance warm ups in our logs as we were used before, we went from every 3-4 minutes to 20-25 minutes. I definitely think things have changed on Google side as we haven't changed anything on our side. But some strange things are still going on at the moment (12/26 0:52 UTC+1) as a dynamic instance has been up for more than 4 hours but has served only one request (cf. screenshot below). Thanx again Saket for your help. François https://lh6.googleusercontent.com/-ARDAA2Yu-NY/UNo-Bgn9SpI/yN8/NNC4QLzi93g/s1600/Instances+-+VinoCities+-+Google+Chrome.jpg On Monday, December 24, 2012 11:54:48 PM UTC+1, Saket Kumar wrote: Hi Francois, Are you still facing this issue? I did a small test for your application and didn't find anything too bad from scheduler's perspective. I'm trying to understand if it was a temporary glitch that was causing the issue or something is wrong with scheduler's algorithm. Or if scheduler doesn't spin instances properly if QPS is low. Here is series of events- a.) Single resident was serving for 1 day, 03:26:37 minutes, serving 9600 request b.) After serving 96 requests with raised QPS, new instance was created. c.) QPS lowered and the new instance was allowed to die. d.) Again the QPS was increased and new instance was created. Both instances were handling requests at this point. e.) QPS lowered again, newly formed instance dies and older instance starts serving 100% of the requests. - Saket On Saturday, 22 December 2012 12:18:00 UTC+1, Francois Masurel wrote: Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks, Christina On Fri, Dec 21, 2012 at 8:39 AM, Carl Schroeder schroede...@gmail.comwrote: I've been sacrificing unicorns to dark powers...clearly I have been doing it wrong. That probably explains some unusual behavior in other parts of my app. AFK pentagrams. :( On Thursday, December 20, 2012 7:51:35 PM UTC-8, Cesium wrote: Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that I sprinkled rainbow Skittles across the floor to attract the unicorns. They're back! David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFdFH0ZqWbgJ. To post to this group, send email to google-a...@googlegroups.com. To unsubscribe from this group, send email to google-appengi...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Christina Ilvento | Google App Engine | cilv...@google.com | (650)-201-9399 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/CYkGQEaDc-gJ. To post to this group, send email to google-appengine@googlegroups.com. To
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Hi Cesium, Can you share your app-id as well? Thanks! Saket On Monday, 17 December 2012 16:32:40 UTC+1, Cesium wrote: On Dec 16, something changed. Now, instances do not survive more than a couple minutes of inactivity (no incoming requests). Thus, low traffic applications see long latency since a new instance is created for the request. This is disastrous for my application (and customers). Can someone please help? Thanks, David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/LOXI1o2m_dgJ. To post to this group, send email to google-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Hi Francois, Are you still facing this issue? I did a small test for your application and didn't find anything too bad from scheduler's perspective. I'm trying to understand if it was a temporary glitch that was causing the issue or something is wrong with scheduler's algorithm. Or if scheduler doesn't spin instances properly if QPS is low. Here is series of events- a.) Single resident was serving for 1 day, 03:26:37 minutes, serving 9600 request b.) After serving 96 requests with raised QPS, new instance was created. c.) QPS lowered and the new instance was allowed to die. d.) Again the QPS was increased and new instance was created. Both instances were handling requests at this point. e.) QPS lowered again, newly formed instance dies and older instance starts serving 100% of the requests. - Saket On Saturday, 22 December 2012 12:18:00 UTC+1, Francois Masurel wrote: Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks, Christina On Fri, Dec 21, 2012 at 8:39 AM, Carl Schroeder schroede...@gmail.comwrote: I've been sacrificing unicorns to dark powers...clearly I have been doing it wrong. That probably explains some unusual behavior in other parts of my app. AFK pentagrams. :( On Thursday, December 20, 2012 7:51:35 PM UTC-8, Cesium wrote: Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that I sprinkled rainbow Skittles across the floor to attract the unicorns. They're back! David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFdFH0ZqWbgJ. To post to this group, send email to google-a...@googlegroups.com. To unsubscribe from this group, send email to google-appengi...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Christina Ilvento | Google App Engine | cilv...@google.com | (650)-201-9399 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/3hvbGCAdzBAJ. To post to this group, send email to google-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Hi Christina, For my personal case, my production app-id is vncts1 with billing enabled. And the related issue is : https://code.google.com/p/googleappengine/issues/detail?id=7865 As I said at the beginning of this thread, there are quite a few other threads related to this problem : https://groups.google.com/forum/#!msg/google-appengine/cJcOrOE4JDc/uKFBbylFOxIJ https://groups.google.com/d/msg/google-appengine/8KiXRP-oU5I/Jf5kzcvyIiwJ https://groups.google.com/d/msg/google-appengine/NR_oV4znvks/KtkSmVQD2IgJ https://groups.google.com/d/msg/google-appengine/_znmrJwFMuM/V2epYOQ19L4J https://groups.google.com/d/topic/google-appengine/hg3BH8WOGWA/discussion https://groups.google.com/d/topic/google-appengine/UN5oCWkPsaA/discussion https://groups.google.com/d/topic/google-appengine/RneC9qDbeRE/discussion https://groups.google.com/d/topic/google-appengine/sLZcZoK-A3Y/discussion Thanx for you help. François On Saturday, December 22, 2012 3:15:05 AM UTC+1, Christina Ilvento wrote: Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks, Christina On Fri, Dec 21, 2012 at 8:39 AM, Carl Schroeder schroede...@gmail.comjavascript: wrote: I've been sacrificing unicorns to dark powers...clearly I have been doing it wrong. That probably explains some unusual behavior in other parts of my app. AFK pentagrams. :( On Thursday, December 20, 2012 7:51:35 PM UTC-8, Cesium wrote: Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that I sprinkled rainbow Skittles across the floor to attract the unicorns. They're back! David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFdFH0ZqWbgJ. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. -- Christina Ilvento | Google App Engine | cilv...@google.com javascript: | (650)-201-9399 -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/FsXV5IpSNpAJ. To post to this group, send email to google-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
cronentries cron url/some-non-static-url/url scheduleevery 1 minutes/schedule /cron /cronentries This will keep one instance warm. Jeff -- 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-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
I've been sacrificing unicorns to dark powers...clearly I have been doing it wrong. That probably explains some unusual behavior in other parts of my app. AFK pentagrams. :( On Thursday, December 20, 2012 7:51:35 PM UTC-8, Cesium wrote: Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that I sprinkled rainbow Skittles across the floor to attract the unicorns. They're back! David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFdFH0ZqWbgJ. To post to this group, send email to google-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Hi All, Would you mind sending app-ids that you're seeing this behavior for? Please feel free to send them to me directly or to link any issues you have filed in our issue tracker so that we can investigate. Thanks, Christina On Fri, Dec 21, 2012 at 8:39 AM, Carl Schroeder schroeder.car...@gmail.comwrote: I've been sacrificing unicorns to dark powers...clearly I have been doing it wrong. That probably explains some unusual behavior in other parts of my app. AFK pentagrams. :( On Thursday, December 20, 2012 7:51:35 PM UTC-8, Cesium wrote: Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that I sprinkled rainbow Skittles across the floor to attract the unicorns. They're back! David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MFdFH0ZqWbgJ. To post to this group, send email to google-appengine@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. -- Christina Ilvento | Google App Engine | cilve...@google.com | (650)-201-9399 -- 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-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
GAE is still spinning up and down instances rapidly with little rhyme or reason. Unless the reason is to book lots of warmup CPU hours. On Tuesday, December 18, 2012 11:57:11 AM UTC-8, Cesium wrote: Reasoned logic will get us nowhere with this issue. On Dec 18, 2012 11:48 AM, Michael Hermus michael...@gmail.comjavascript: wrote: This is mind boggling. There is a simple, brain-dead fix that does NOT require the (presumably complex) scheduling logic to change one bit. Simply NEVER expose a user-facing request to a loading request, if the developer configures it that way. Let the scheduler spin up and down instances however it sees fit, but don't let a new instance serve requests until it successfully completes initialization. This was beat to death months ago in a series of threads, but obviously resulted in no action. On Tuesday, December 18, 2012 12:03:19 PM UTC-5, Cesium wrote: I changed my settings to have 3 resident instances. I still see long latency when the scheduler creates new instances, rather than using the resident instances. The GAE scheduler behavior at low request rates is odd, and counterintuitive. But we knew that didn't we? David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/mibjVETUupIJ. To post to this group, send email to google-a...@googlegroups.comjavascript: . To unsubscribe from this group, send email to google-appengi...@googlegroups.com javascript:. 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 view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/kd7bDt7fyhAJ. To post to this group, send email to google-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Ready for this? Now, a single instance survives for hours and hours, happily serving requests with the usual low latency response time. This is just what Sir Brandon wrote about. Mysterious changes in the system's behavior. I should note that I sprinkled rainbow Skittles across the floor to attract the unicorns. They're back! David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/aqCfpJ2SlV0J. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
+1 On Tuesday, December 18, 2012 5:57:52 PM UTC-5, Carl Schroeder wrote: I should add code so that whenever an instance spins up to a URL that is not a warmup, it sends an email to the GAE devs. Perhaps I will try it on a free app first, just to get the kinks out... ;) On Monday, December 17, 2012 7:32:40 AM UTC-8, Cesium wrote: On Dec 16, something changed. Now, instances do not survive more than a couple minutes of inactivity (no incoming requests). Thus, low traffic applications see long latency since a new instance is created for the request. This is disastrous for my application (and customers). Can someone please help? Thanks, David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/4JAl1B3PWcgJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
By the way, if anyone interested has not starred the relevant issue in the issue tracker, please do so! https://code.google.com/p/googleappengine/issues/detail?id=7865 On Monday, December 17, 2012 10:32:40 AM UTC-5, Cesium wrote: On Dec 16, something changed. Now, instances do not survive more than a couple minutes of inactivity (no incoming requests). Thus, low traffic applications see long latency since a new instance is created for the request. This is disastrous for my application (and customers). Can someone please help? Thanks, David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/9Vjt8631gGcJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Thanks for putting the stress in my vacation this week, Appengine Team. David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/1GsZFmLdX2gJ. To post to this group, send email to google-appengine@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.
Re: [google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Reasoned logic will get us nowhere with this issue. On Dec 18, 2012 11:48 AM, Michael Hermus michael.her...@gmail.com wrote: This is mind boggling. There is a simple, brain-dead fix that does NOT require the (presumably complex) scheduling logic to change one bit. Simply NEVER expose a user-facing request to a loading request, if the developer configures it that way. Let the scheduler spin up and down instances however it sees fit, but don't let a new instance serve requests until it successfully completes initialization. This was beat to death months ago in a series of threads, but obviously resulted in no action. On Tuesday, December 18, 2012 12:03:19 PM UTC-5, Cesium wrote: I changed my settings to have 3 resident instances. I still see long latency when the scheduler creates new instances, rather than using the resident instances. The GAE scheduler behavior at low request rates is odd, and counterintuitive. But we knew that didn't we? David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/mibjVETUupIJ. To post to this group, send email to google-appengine@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. -- 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-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
I changed my settings to have 3 resident instances. I still see long latency when the scheduler creates new instances, rather than using the resident instances. The GAE scheduler behavior at low request rates is odd, and counterintuitive. But we knew that didn't we? David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/ye1piKeSaoAJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
I have the same problem. We need to migrate away from Java on GAE, I fear it will *never* work right with long instance spinup times. Google gets their instance scheduler half-way working, then make some breaking change that crushes the user experience for low traffic applications. On Tuesday, December 18, 2012 9:03:19 AM UTC-8, Cesium wrote: I changed my settings to have 3 resident instances. I still see long latency when the scheduler creates new instances, rather than using the resident instances. The GAE scheduler behavior at low request rates is odd, and counterintuitive. But we knew that didn't we? David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/g45_Rf7kTLUJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
This is mind boggling. There is a simple, brain-dead fix that does NOT require the (presumably complex) scheduling logic to change one bit. Simply NEVER expose a user-facing request to a loading request, if the developer configures it that way. Let the scheduler spin up and down instances however it sees fit, but don't let a new instance serve requests until it successfully completes initialization. This was beat to death months ago in a series of threads, but obviously resulted in no action. On Tuesday, December 18, 2012 12:03:19 PM UTC-5, Cesium wrote: I changed my settings to have 3 resident instances. I still see long latency when the scheduler creates new instances, rather than using the resident instances. The GAE scheduler behavior at low request rates is odd, and counterintuitive. But we knew that didn't we? David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/mibjVETUupIJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
What chaps my hide is the unannounced CHANGE in the behavior (for my app). I have been running for months with a single instance and no problems. Then, it breaks. No warning. No feedback. No drinks. No dinner. Nada. I have stayed out of the discussion because all was well. Oh, and, Takashi, don't bother this time. I have designed a non-appengine solution. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/5j_Xhjz_zakJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
I hate when my hide gets chapped. And drinks would help... Good luck out there. On Tuesday, December 18, 2012 3:18:03 PM UTC-5, Cesium wrote: What chaps my hide is the unannounced CHANGE in the behavior (for my app). I have been running for months with a single instance and no problems. Then, it breaks. No warning. No feedback. No drinks. No dinner. Nada. I have stayed out of the discussion because all was well. Oh, and, Takashi, don't bother this time. I have designed a non-appengine solution. -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/yust4nLrVKIJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Yep you're right, adding some more resident instances doesn't fix the problem, the scheduler is definitively broken. Feeling desperate. On Tuesday, December 18, 2012 6:03:19 PM UTC+1, Cesium wrote: I changed my settings to have 3 resident instances. I still see long latency when the scheduler creates new instances, rather than using the resident instances. The GAE scheduler behavior at low request rates is odd, and counterintuitive. But we knew that didn't we? David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Zm9BXhOHQZcJ. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
I should add code so that whenever an instance spins up to a URL that is not a warmup, it sends an email to the GAE devs. Perhaps I will try it on a free app first, just to get the kinks out... ;) On Monday, December 17, 2012 7:32:40 AM UTC-8, Cesium wrote: On Dec 16, something changed. Now, instances do not survive more than a couple minutes of inactivity (no incoming requests). Thus, low traffic applications see long latency since a new instance is created for the request. This is disastrous for my application (and customers). Can someone please help? Thanks, David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/lJl0VKycht8J. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
Related screenshot : https://lh6.googleusercontent.com/-NC53S0zotzw/UNEBXIUsneI/xoU/IdGvczL6eTQ/s1600/Instances+-+VinoCities+-+Google+Chrome_3.jpg On Tuesday, December 18, 2012 11:23:15 PM UTC+1, Francois Masurel wrote: Yep you're right, adding some more resident instances doesn't fix the problem, the scheduler is definitively broken. Feeling desperate. On Tuesday, December 18, 2012 6:03:19 PM UTC+1, Cesium wrote: I changed my settings to have 3 resident instances. I still see long latency when the scheduler creates new instances, rather than using the resident instances. The GAE scheduler behavior at low request rates is odd, and counterintuitive. But we knew that didn't we? David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/XDCahIPYuK0J. To post to this group, send email to google-appengine@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.
[google-appengine] Re: Urgent, Need Help: Instances are shutting down after a couple minutes of inactivity.
I fear that Sir Brandon has given us a fair assesment of GAE and GAE support. The unicorns have left the building. David -- You received this message because you are subscribed to the Google Groups Google App Engine group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/zjjqI_yrM5wJ. To post to this group, send email to google-appengine@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.
