[appengine-java] Re: WARNING: 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
I prefer to see the message if it is going to be slow for one time, but it takes too much time(5 to 10s). In my situation, I am measuring how a simple url performs from a different network(here google) and the numbers are misleading. I call 10 URL and run only once in 10 minutes and every time a new process has to be started and numbers are high. I starred it Thanks, Narayan On May 5, 9:57 am, Jake jbrooko...@cast.org wrote: I believe the general thought is that any persistence problems caused by a recycled application are to be expected and you should work to handle those issues. Sessions can be used to hold state, but application variables need to be able to recover from an application restart (or a newly spawned instance). As for lasting longer, I totally agree - I'm also running mine on a small scale and reload requests happen far too frequently. See and Star:http://code.google.com/p/googleappengine/issues/detail?id=2931 Jake On May 5, 9:48 am, Christian Goudreau goudreau.christ...@gmail.com wrote: And what about app that will no see their traffic grows ? Mine is mostly an intranet and it's annoying to see how slow it is because of those sleep time... Is it possible to make them last longer ? I even get some persistance problems when it goes to sleep... I'm using guiceFilters with the command pattern and I have to do a simple put in two-three request each time because of that. Christian On Thu, Apr 22, 2010 at 3:19 PM, Ikai L (Google) ika...@google.com wrote: You're getting this warning because your requests are mostly loading requests. As your traffic grows, this will go away, since less of your requests will be startup requests. It's there to tell you that your app isn't running slow - it's taking more time than it normally should because of initialization. Nevertheless, I think the general feedback has been it's a great feature, but I'd like to turn it off or hide it. I'l raise this with the team. On Thu, Apr 22, 2010 at 3:33 AM, Abhimanyu Saxena abhimanyusax...@gmail.com wrote: so what does it mean? I am repeatedly getting this warning with my app... is there anything that I can do for it ? On Apr 22, 7:24 am, Tristan tristan.slomin...@gmail.com wrote: Is it possible to make it an INFO and not a WARNING? Should I start an issue? As a programmer, I really don't have any direct control over this. All the WARNINGS are just masking other important issues that should be warnings. On Apr 21, 1:33 pm, Ikai L (Google) ika...@google.com wrote: Yep, we're rolling this out slowly with the 1.3.3 release to let developers know that some requests are slow because they are startup requests. On Wed, Apr 21, 2010 at 6:09 AM, Tristan tristan.slomin...@gmail.com wrote: Hey, I started seeing when a task queue starts now: WARNING: 200 OK 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. instead of this WARNING: 500 Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.htmlformoredetails. I like it. Is this the expected behavior from now on? Tristan -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- Ikai Lan Developer Relations, Google App Engine Twitter:http://twitter.com/ikai Delicious:http://delicious.com/ikailan Google App Engine links: Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group athttp://
[appengine-java] Re: WARNING: 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
I believe the general thought is that any persistence problems caused by a recycled application are to be expected and you should work to handle those issues. Sessions can be used to hold state, but application variables need to be able to recover from an application restart (or a newly spawned instance). As for lasting longer, I totally agree - I'm also running mine on a small scale and reload requests happen far too frequently. See and Star: http://code.google.com/p/googleappengine/issues/detail?id=2931 Jake On May 5, 9:48 am, Christian Goudreau goudreau.christ...@gmail.com wrote: And what about app that will no see their traffic grows ? Mine is mostly an intranet and it's annoying to see how slow it is because of those sleep time... Is it possible to make them last longer ? I even get some persistance problems when it goes to sleep... I'm using guiceFilters with the command pattern and I have to do a simple put in two-three request each time because of that. Christian On Thu, Apr 22, 2010 at 3:19 PM, Ikai L (Google) ika...@google.com wrote: You're getting this warning because your requests are mostly loading requests. As your traffic grows, this will go away, since less of your requests will be startup requests. It's there to tell you that your app isn't running slow - it's taking more time than it normally should because of initialization. Nevertheless, I think the general feedback has been it's a great feature, but I'd like to turn it off or hide it. I'l raise this with the team. On Thu, Apr 22, 2010 at 3:33 AM, Abhimanyu Saxena abhimanyusax...@gmail.com wrote: so what does it mean? I am repeatedly getting this warning with my app... is there anything that I can do for it ? On Apr 22, 7:24 am, Tristan tristan.slomin...@gmail.com wrote: Is it possible to make it an INFO and not a WARNING? Should I start an issue? As a programmer, I really don't have any direct control over this. All the WARNINGS are just masking other important issues that should be warnings. On Apr 21, 1:33 pm, Ikai L (Google) ika...@google.com wrote: Yep, we're rolling this out slowly with the 1.3.3 release to let developers know that some requests are slow because they are startup requests. On Wed, Apr 21, 2010 at 6:09 AM, Tristan tristan.slomin...@gmail.com wrote: Hey, I started seeing when a task queue starts now: WARNING: 200 OK 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. instead of this WARNING: 500 Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.htmlformoredetails. I like it. Is this the expected behavior from now on? Tristan -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- Ikai Lan Developer Relations, Google App Engine Twitter:http://twitter.com/ikai Delicious:http://delicious.com/ikailan Google App Engine links: Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group athttp:// groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2bunsubscr...@googlegroups.com . For more options, visit this group athttp:// groups.google.com/group/google-appengine-java?hl=en. -- You received this message
[appengine-java] Re: WARNING: 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
Hi Ikai, where can I get a more specific response to this issue? I find it odd something like this would happen in first place (my app hangs for about 7 seconds awaiting for the process to fire up). I tried pinging my app every 2 minutes hoping the process would not go to sleep ... to no effect. Please advise -- this is very frustrating. Andi On Apr 21, 2:33 pm, Ikai L (Google) ika...@google.com wrote: Yep, we're rolling this out slowly with the 1.3.3 release to let developers know that some requests are slow because they are startup requests. On Wed, Apr 21, 2010 at 6:09 AM, Tristan tristan.slomin...@gmail.comwrote: Hey, I started seeing when a task queue starts now: WARNING: 200 OK 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. instead of this WARNING: 500 Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.htmlfor more details. I like it. Is this the expected behavior from now on? Tristan -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- Ikai Lan Developer Relations, Google App Engine Twitter:http://twitter.com/ikai Delicious:http://delicious.com/ikailan Google App Engine links: Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: WARNING: 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
Hey Andi, It goes something like this as far as I understand it. Your app lives in a process. When requests come in, those requests are handed to the app process to do what it needs to do and send a response. When request A comes in and there are no active processes, the app process starts up (the 7 seconds you see) in order to handle request A. Let's say that while it is handling request A, request B, C, D, and E come in. Because the process is busy handling A, the new requests (B, C, D, and E) are put on a queue. There is some magic calculation that goes on here that involves a few things. If the calculation sees that your process can handle a request very fast, it piles more requests on the queue, so that the queue could be B:C:D:E because it has faith that response will happen in reasonable time. On the other hand, if the calculation sees that your process is taking it's sweet time, it decides to start another process (another 7 seconds you see), and then gives the next request in the queue (B) to that process to ensure that the very last request on the queue - E gets served in reasonable time. After some time period when a process has no requests waiting in the queue, it kills itself. From what I read, it takes on average 1 request per second to keep process from giving up on the world of the living. If you look at the appengine roadmap, reserved instances are there. So pretty soon we'll be able to pay for having a process staying alive to server requests. I may be wrong. Cheers, Tristan On Apr 26, 10:44 pm, AndiMullaraj andimulla...@gmail.com wrote: Hi Ikai, where can I get a more specific response to this issue? I find it odd something like this would happen in first place (my app hangs for about 7 seconds awaiting for the process to fire up). I tried pinging my app every 2 minutes hoping the process would not go to sleep ... to no effect. Please advise -- this is very frustrating. Andi On Apr 21, 2:33 pm, Ikai L (Google) ika...@google.com wrote: Yep, we're rolling this out slowly with the 1.3.3 release to let developers know that some requests are slow because they are startup requests. On Wed, Apr 21, 2010 at 6:09 AM, Tristan tristan.slomin...@gmail.comwrote: Hey, I started seeing when a task queue starts now: WARNING: 200 OK 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. instead of this WARNING: 500 Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.htmlformore details. I like it. Is this the expected behavior from now on? Tristan -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- Ikai Lan Developer Relations, Google App Engine Twitter:http://twitter.com/ikai Delicious:http://delicious.com/ikailan Google App Engine links: Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: WARNING: 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
so what does it mean? I am repeatedly getting this warning with my app... is there anything that I can do for it ? On Apr 22, 7:24 am, Tristan tristan.slomin...@gmail.com wrote: Is it possible to make it an INFO and not a WARNING? Should I start an issue? As a programmer, I really don't have any direct control over this. All the WARNINGS are just masking other important issues that should be warnings. On Apr 21, 1:33 pm, Ikai L (Google) ika...@google.com wrote: Yep, we're rolling this out slowly with the 1.3.3 release to let developers know that some requests are slow because they are startup requests. On Wed, Apr 21, 2010 at 6:09 AM, Tristan tristan.slomin...@gmail.comwrote: Hey, I started seeing when a task queue starts now: WARNING: 200 OK 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. instead of this WARNING: 500 Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.htmlformore details. I like it. Is this the expected behavior from now on? Tristan -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- Ikai Lan Developer Relations, Google App Engine Twitter:http://twitter.com/ikai Delicious:http://delicious.com/ikailan Google App Engine links: Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: WARNING: 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
Is it possible to make it an INFO and not a WARNING? Should I start an issue? As a programmer, I really don't have any direct control over this. All the WARNINGS are just masking other important issues that should be warnings. On Apr 21, 1:33 pm, Ikai L (Google) ika...@google.com wrote: Yep, we're rolling this out slowly with the 1.3.3 release to let developers know that some requests are slow because they are startup requests. On Wed, Apr 21, 2010 at 6:09 AM, Tristan tristan.slomin...@gmail.comwrote: Hey, I started seeing when a task queue starts now: WARNING: 200 OK 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. instead of this WARNING: 500 Request was aborted after waiting too long to attempt to service your request. Most likely, this indicates that you have reached your simultaneous dynamic request limit. This is almost always due to excessively high latency in your app. Please see http://code.google.com/appengine/docs/quotas.htmlfor more details. I like it. Is this the expected behavior from now on? Tristan -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.comgoogle-appengine-java%2B unsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en. -- Ikai Lan Developer Relations, Google App Engine Twitter:http://twitter.com/ikai Delicious:http://delicious.com/ikailan Google App Engine links: Blog:http://googleappengine.blogspot.com Twitter:http://twitter.com/app_engine Reddit:http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group athttp://groups.google.com/group/google-appengine-java?hl=en. -- You received this message because you are subscribed to the Google Groups Google App Engine for Java group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
