Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-24 Thread muhammad . taiyab
Thanks Vinny P for your reply,

I have increased the number of idle instances from Automatic to 100 and 
lower the minimum pending latency slider from Automatic to 100ms. I will 
update in few days if I faced this issue again.

On Saturday, August 24, 2013 8:15:07 AM UTC+5, Vinny P wrote:

 On Fri, Aug 23, 2013 at 2:38 AM, M Taiyab @ K2-Labs wrote:

 I am again facing this error on my few applications. More than 
 12,000 hits failed with this error in last 24 hours (about 26%) on my 
 billing enabled instance. Can anyone tell me what is happening?

  

  
  
 Can you increase the number of idle instances and lower the minimum 
 pending latency slider on your admin console? See 
 https://developers.google.com/appengine/docs/adminconsole/performancesettings#scheduler
  
 Try it out for a day and see if the app's performance improves.

  -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.com
   
  

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-24 Thread Alex Burgel
On Saturday, August 24, 2013 11:12:35 AM UTC-7, muhamma...@k2-labs.com 
wrote:

 Thanks Vinny P for your reply,

 I have increased the number of idle instances from Automatic to 100 and 
 lower the minimum pending latency slider from Automatic to 100ms. I will 
 update in few days if I faced this issue again.


Did you change the _minimum_ number of idle instances to 100? Because that 
means you will pay for at least 100 instances per hour, which, at $0.08 per 
hour, is $192 per day. Just wanted to give you a heads up on that so you 
don't get shocked by your next bill.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-24 Thread muhammad . taiyab
Hi Alex,

Thanks for letting me know, I have updated this value to 50 instances. If 
it worked then I will again update this to minimum working value for my 
application.

On Saturday, August 24, 2013 11:36:36 PM UTC+5, Alex Burgel wrote:

 On Saturday, August 24, 2013 11:12:35 AM UTC-7, muhamma...@k2-labs.comwrote:

 Thanks Vinny P for your reply,

 I have increased the number of idle instances from Automatic to 100 and 
 lower the minimum pending latency slider from Automatic to 100ms. I will 
 update in few days if I faced this issue again.


 Did you change the _minimum_ number of idle instances to 100? Because that 
 means you will pay for at least 100 instances per hour, which, at $0.08 per 
 hour, is $192 per day. Just wanted to give you a heads up on that so you 
 don't get shocked by your next bill.


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-23 Thread muhammad . taiyab
I am again facing this error on my few applications. More than 12,000 hits 
failed with this error in last 24 hours (about 26%) on my billing enabled 
instance. Can anyone tell me what is happening?

On Thursday, August 22, 2013 5:08:43 PM UTC+5, muhamma...@k2-labs.com wrote:

 I am not sure about the exact error. The request doesn't reach my code. I 
 have few log printings in my code that doesn't get printed. What I see in 
 AppEngine logs is the following text.
 Request was aborted after waiting too long to attempt to service your 
 request.

 I have observed that this issue mostly occurs when there are less no. of 
 users (At midnight). This is only true for my production servers. On QA 
 servers there is no big difference.

 On Thursday, August 22, 2013 3:14:33 PM UTC+5, timh wrote:

 When you say timeout do you actually mean DeadlineExceededError ?
 Does this occurr when the instance is starting up or with already running 
 instances ?

 T

 On Thursday, August 22, 2013 1:48:05 PM UTC+8, muhamma...@k2-labs.comwrote:

 Hi Vinny P,

 Thanks for your reply.

 The issue occurs mostly between 11pm to 1am UTC. At that time all of my 
 applications start giving error, even my applications that are only used by 
 small number of QA users. Most of the services use only Datastore 
 read/write calls and data processing.

 Moving to the Python 2.7 runtime and the HRD datastore seems difficult 
 for our big applications code at this time.

 On Wednesday, August 21, 2013 11:59:30 PM UTC+5, Vinny P wrote:

 On Tue, Aug 20, 2013 at 2:38 AM, Taiyab @ K2-Labs wrote:

 I am getting the following errors on all of my AppEngine apps and 
 unable to connect to server.
 Request was aborted after waiting too long to attempt to service your 
 request.
 I am using Python 2.5 runtime and Master/Slave datastore
 I am facing this issue very frequently almost daily about 11pm to 1am 
 UTC. Do anyone know what is the issue?

  
  Is there anything special about that time frame for your application 
 (for example, do you have extremely low/high traffic levels at that time)? 
 Are you attempting to connect to an external service, and if so, what 
 services are they? Are you doing any initialization work?
  
 As a short term measure, try increasing the number of idle instances 
 allocated.
  
 I also recommend that you move to the Python 2.7 runtime and the HRD 
 datastore, those two steps alone will dramatically improve your 
 application.
  
   
 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.com
  


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-23 Thread Vinny P
On Fri, Aug 23, 2013 at 2:38 AM, muhammad.tai...@k2-labs.com wrote:

 I am again facing this error on my few applications. More than 12,000 hits
 failed with this error in last 24 hours (about 26%) on my billing enabled
 instance. Can anyone tell me what is happening?





Can you increase the number of idle instances and lower the minimum pending
latency slider on your admin console? See
https://developers.google.com/appengine/docs/adminconsole/performancesettings#scheduler

Try it out for a day and see if the app's performance improves.

 -
-Vinny P
Technology  Media Advisor
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-22 Thread timh
When you say timeout do you actually mean DeadlineExceededError ?
Does this occurr when the instance is starting up or with already running 
instances ?

T

On Thursday, August 22, 2013 1:48:05 PM UTC+8, muhamma...@k2-labs.com wrote:

 Hi Vinny P,

 Thanks for your reply.

 The issue occurs mostly between 11pm to 1am UTC. At that time all of my 
 applications start giving error, even my applications that are only used by 
 small number of QA users. Most of the services use only Datastore 
 read/write calls and data processing.

 Moving to the Python 2.7 runtime and the HRD datastore seems difficult for 
 our big applications code at this time.

 On Wednesday, August 21, 2013 11:59:30 PM UTC+5, Vinny P wrote:

 On Tue, Aug 20, 2013 at 2:38 AM, Taiyab @ K2-Labs wrote:

 I am getting the following errors on all of my AppEngine apps and unable 
 to connect to server.
 Request was aborted after waiting too long to attempt to service your 
 request.
 I am using Python 2.5 runtime and Master/Slave datastore
 I am facing this issue very frequently almost daily about 11pm to 1am UTC. 
 Do 
 anyone know what is the issue?

  
  Is there anything special about that time frame for your application 
 (for example, do you have extremely low/high traffic levels at that time)? 
 Are you attempting to connect to an external service, and if so, what 
 services are they? Are you doing any initialization work?
  
 As a short term measure, try increasing the number of idle instances 
 allocated.
  
 I also recommend that you move to the Python 2.7 runtime and the HRD 
 datastore, those two steps alone will dramatically improve your application.
  
   
 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.com
  


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-22 Thread muhammad . taiyab
I am not sure about the exact error. The request doesn't reach my code. I 
have few log printings in my code that doesn't get printed. What I see in 
AppEngine logs is the following text.
Request was aborted after waiting too long to attempt to service your 
request.

I have observed that this issue mostly occurs when there are less no. of 
users (At midnight). This is only true for my production servers. On QA 
servers there is no big difference.

On Thursday, August 22, 2013 3:14:33 PM UTC+5, timh wrote:

 When you say timeout do you actually mean DeadlineExceededError ?
 Does this occurr when the instance is starting up or with already running 
 instances ?

 T

 On Thursday, August 22, 2013 1:48:05 PM UTC+8, muhamma...@k2-labs.comwrote:

 Hi Vinny P,

 Thanks for your reply.

 The issue occurs mostly between 11pm to 1am UTC. At that time all of my 
 applications start giving error, even my applications that are only used by 
 small number of QA users. Most of the services use only Datastore 
 read/write calls and data processing.

 Moving to the Python 2.7 runtime and the HRD datastore seems difficult 
 for our big applications code at this time.

 On Wednesday, August 21, 2013 11:59:30 PM UTC+5, Vinny P wrote:

 On Tue, Aug 20, 2013 at 2:38 AM, Taiyab @ K2-Labs wrote:

 I am getting the following errors on all of my AppEngine apps and 
 unable to connect to server.
 Request was aborted after waiting too long to attempt to service your 
 request.
 I am using Python 2.5 runtime and Master/Slave datastore
 I am facing this issue very frequently almost daily about 11pm to 1am 
 UTC. Do anyone know what is the issue?

  
  Is there anything special about that time frame for your application 
 (for example, do you have extremely low/high traffic levels at that time)? 
 Are you attempting to connect to an external service, and if so, what 
 services are they? Are you doing any initialization work?
  
 As a short term measure, try increasing the number of idle instances 
 allocated.
  
 I also recommend that you move to the Python 2.7 runtime and the HRD 
 datastore, those two steps alone will dramatically improve your application.
  
   
 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.com
  


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-21 Thread Vinny P
On Tue, Aug 20, 2013 at 2:38 AM, muhammad.tai...@k2-labs.com wrote:

 I am getting the following errors on all of my AppEngine apps and unable
 to connect to server.
 Request was aborted after waiting too long to attempt to service your
 request.
 I am using Python 2.5 runtime and Master/Slave datastore
 I am facing this issue very frequently almost daily about 11pm to 1am UTC. Do
 anyone know what is the issue?


 Is there anything special about that time frame for your application (for
example, do you have extremely low/high traffic levels at that time)? Are
you attempting to connect to an external service, and if so, what services
are they? Are you doing any initialization work?

As a short term measure, try increasing the number of idle instances
allocated.

I also recommend that you move to the Python 2.7 runtime and the HRD
datastore, those two steps alone will dramatically improve your application.


-
-Vinny P
Technology  Media Advisor
Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


Re: [google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-21 Thread muhammad . taiyab
Hi Vinny P,

Thanks for your reply.

The issue occurs mostly between 11pm to 1am UTC. At that time all of my 
applications start giving error, even my applications that are only used by 
small number of QA users. Most of the services use only Datastore 
read/write calls and data processing.

Moving to the Python 2.7 runtime and the HRD datastore seems difficult for 
our big applications code at this time.

On Wednesday, August 21, 2013 11:59:30 PM UTC+5, Vinny P wrote:

 On Tue, Aug 20, 2013 at 2:38 AM, Taiyab @ K2-Labs wrote:

 I am getting the following errors on all of my AppEngine apps and unable 
 to connect to server.
 Request was aborted after waiting too long to attempt to service your 
 request.
 I am using Python 2.5 runtime and Master/Slave datastore
 I am facing this issue very frequently almost daily about 11pm to 1am UTC. 
 Do 
 anyone know what is the issue?

  
  Is there anything special about that time frame for your application (for 
 example, do you have extremely low/high traffic levels at that time)? Are 
 you attempting to connect to an external service, and if so, what services 
 are they? Are you doing any initialization work?
  
 As a short term measure, try increasing the number of idle instances 
 allocated.
  
 I also recommend that you move to the Python 2.7 runtime and the HRD 
 datastore, those two steps alone will dramatically improve your application.
  
   
 -
 -Vinny P
 Technology  Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.com
  


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.


[google-appengine] Unable to connect to GAE apps due to Timeout errors

2013-08-20 Thread muhammad . taiyab
Hi GAE team,

I am getting the following errors on all of my AppEngine apps and unable to 
connect to server.

Request was aborted after waiting too long to attempt to service your 
request.

I am using Python 2.5 runtime and Master/Slave datastore

I am facing this issue very frequently almost daily about 11pm to 1am UTC. Do 
anyone know what is the issue?

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.