Re: [google-appengine] Front-End instances shutting down

[Mos]

Same with my application for days. Google, please fix this again.


2014-01-25 

> Hi,
> All my front end instances are shutting down after a few requests or a few
> seconds after they handle one, causing every new request to spin up a new
> instance and responding very slow !!!
> Is anyone experiencing this as well ??
>
> @Google
> How can we as developers put our apps in gae if things like that happens
> so often ?  Why is it not mentioned in the app engine downtime notify ?
>
> --
> 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.
>

-- 
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] Front-End instances shutting down

[Stefano Ciccarelli]

As said in other threads: +1

Il sabato 25 gennaio 2014,  ha scritto:

> Hi,
> All my front end instances are shutting down after a few requests or a few
> seconds after they handle one, causing every new request to spin up a new
> instance and responding very slow !!!
> Is anyone experiencing this as well ??
>
> @Google
> How can we as developers put our apps in gae if things like that happens
> so often ?  Why is it not mentioned in the app engine downtime notify ?
>
> --
> 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  'cvml', 'google-appengine%2bunsubscr...@googlegroups.com');>.
> To post to this group, send email to 
> google-appengine@googlegroups.com '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.
>


-- 
Nel mondo esistono 10 categorie di persone, quelle che capiscono il binario
e quelle che non lo capiscono.

-- 
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] High Latency on GoAgent Proxy Server hosted on Google App Engine

[Vinny P]

6.2 requests per minute is a single snapshot of the load the application is
experiencing. What truly matters is spikes in requests and load, not single
arbitrary snapshots in time.

Can you post the instances and requests graphs? You can find them in the
dashboard section.

-
-Vinny P
Technology & Media Advisor
Chicago, IL

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




On Sat, Jan 25, 2014 at 10:56 AM, Nathan Suchy  wrote:

> That is not a lot of traffic 6.2 requests per minute...
>
>
> On Sat, Jan 25, 2014 at 11:55 AM, Nathan Suchy  wrote:
>
>> *Current Load [image: help]
>> * URI Req/Min
>> current Requestslast 24 hrs Runtime MCycleslast hr Avg Latencylast hr
>> /2
>>  6.2 6.93K 9 4516 ms
>>
>>

-- 
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] Cache headers modified by Google Frontend

[Vinny P]

Hi Francois,

As Nicolas said in this post:
https://groups.google.com/forum/#!topic/google-appengine/k3LrZodr-WA the
caching seems to be working correctly. I can see the proper Cache-Control
and Pragma headers in the response when I use Chrome's Developer Tools
screen. Are you still experiencing errors?

If you're still seeing errors on your end, try this tool:
http://www.hurl.it/?url=http://dev.pronocities.com/theme/com.pronocities.theme.base/858/logo_mail.png(Press
the Launch Request button when the page loads). You'll be able to
see the response headers that Hurl.it gets back from the request.




-
-Vinny P
Technology & Media Advisor
Chicago, IL

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




On Sat, Jan 25, 2014 at 11:26 AM, Francois Masurel wrote:

> Hi everybody,
>
> Do you know why cache headers are modified by Google Frontend servers?
>
> Google prohibits my dynamically served static resources to be cached on
> proxy and user sides.
>
> For example, Google set the Expires header to this:
> Expires: Fri, 01 Jan 1990 00:00:00 GMT
>
> And Pragma and Cache-Control to this:
> Pragma: no-cache
> Cache-Control: no-cache, must-revalidate
>
> In my code, both Pragma and Cache-Control are set to public (plus max-age
> for Cache-Control).
>
> Example of problematic resource:
>
> http://dev.pronocities.com/theme/com.pronocities.theme.base/858/logo_mail.png
>
> What is strange is that the same exact code works perfectly fine in other
> apps like this one:
> http://www.vinocities.com/theme/com.vinocities.theme.base/858/logo_mail.png
>
> Anybody knows what's going on? What can I do to fix it?
>
> Thanx for your help.
>
> François
>
> --
> 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.
>

-- 
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] app engine to work in Eclipse needed 1,7 jre what to do?

[Leonidas Savvides]

android should work with 7? basically all should fixed?


On Mon, Jan 20, 2014 at 10:13 PM, Vinny P  wrote:

> On Mon, Jan 20, 2014 at 7:23 AM, LWDLSE  wrote:
>
> app engine to work in Eclipse needed 1,7 jre what to do? I went to Pref >
>> Jave > installed jre > jre and choose 1.7 (7) but same error appear
>>
>
>
> Uninstall all of the Java JRE and JDK installations on your computer
> (including 6 and 7), and then reinstall JDK 7. Map Eclipse to use the fresh
> install of 7.
>
>
> -
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> App Engine Code Samples: http://www.learntogoogleit.com
>
>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/6WB0BBmRTwo/unsubscribe
> .
> To unsubscribe from this group and all its topics, 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.
>

-- 
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] Confirmed! GAE scheduler is stealing computing hours/money.

[Tapir]

On Sunday, January 26, 2014 1:02:19 AM UTC+8, Tapir wrote:
>
>
>
> On Saturday, January 25, 2014 1:45:47 PM UTC+8, Vinny P wrote:
>>
>> On Fri, Jan 24, 2014 at 8:43 PM, Tapir  wrote:
>>
>>> Before converting my app to modules style, the total front instance 
>>> hours were always less than 28 hours.
>>>
>>
>>
>>
>> If you still have a copy of your app before you converted to modules, try 
>> uploading it and checking the performance. But this is most likely not the 
>> fault of the modules service: App Engine seems to be encountering a lot of 
>> "slowtime" this week, and you'll probably find that the errors smooth 
>> themselves out sooner or later.
>>
>
> Aha, I just checked the log, the datastore reading was really slow. A 
> 1-second request speed 1 minute in the past 24 hours.
>

Aha again, there are about 300 such requests every day, so it is about 300 
more minutes are spent on datastore reading.
I think this is the really reason why my app's front end hours went up in 
the past a few days.
 

>  
>
>>   
>>  
>> -
>> -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] Confirmed! GAE scheduler is stealing computing hours/money.

[Tapir]

On Sunday, January 26, 2014 4:39:07 AM UTC+8, Stefano Ciccarelli wrote:
>
> I have defined a servlet, but GAE seems to be very reluctant to use it. 
>
 
If there is not any resident instances for your app, the warmup service may 
make things worse.
 

>
> Il sabato 25 gennaio 2014, Tapir > ha 
> scritto:
>
>> you need define a warmup servlet (you must use java, right?) for the url 
>> /_ah/warmup, 
>> docs: 
>> https://developers.google.com/appengine/docs/java/config/appconfig#using_a_custom_warmup_servlet
>> This method is useless for non billing apps, for this method needs a 
>> wholly initialized instance running at any time.
>>
>>
>>
>>
>> On Sunday, January 26, 2014 1:17:26 AM UTC+8, Stefano Ciccarelli wrote:
>>>
>>> My problem is that I don't have too much /_ah/warmup requests so my 
>>> users waited up to 40/50 seconds to get a response. This is really 
>>> upsetting me, even because it's not the first time. 
>>>
>>> Il sabato 25 gennaio 2014, Tapir  ha scritto:
>>>
>>> I doubt gae scheduler counts the warmup time as billing front computing 
>>> time now.
>>> I remember a googler ever said the warmup time is not counted as billing 
>>> computing time.
>>>
>>> Before migrating my app to modules style, gae scheduler counts my app's 
>>> front end hours as 26.x hours.
>>> After the migration, gae scheduler counts my app's front end hours as 
>>> 29.x hours.
>>>
>>> In the dashboard log, there are 340 /_ah/warmup requests in the last 24 
>>> hours.
>>> Each warmup request will spend 30 seconds. So it is about 170 minutes 
>>> computing time or 3 hours.
>>>
>>> And 29.x - 26.x = 3. So I doubt gae scheduler counts the warmup time as 
>>> billing front computing time now.
>>>
>>> On Saturday, January 25, 2014 3:23:40 PM UTC+8, Tapir wrote:
>>>
>>> My app doesn't encounter slowdown problem.
>>> The problem is my app is over charged.
>>>
>>> On Saturday, January 25, 2014 1:45:47 PM UTC+8, Vinny P wrote:
>>>
>>> On Fri, Jan 24, 2014 at 8:43 PM, Tapir  wrote:
>>>
>>> Before converting my app to modules style, the total front instance 
>>> hours were always less than 28 hours.
>>>
>>>
>>>
>>>
>>> If you still have a copy of your app before you converted to modules, 
>>> try uploading it and checking the performance. But this is most likely not 
>>> the fault of the modules service: App Engine seems to be encountering a lot 
>>> of "slowtime" this week, and you'll probably find that the errors smooth 
>>> themselves out sooner or later.
>>>   
>>>  
>>> -
>>> -Vinny P
>>> Technology & Media Advisor
>>> Chicago, IL
>>>
>>>   -- 
>> 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.
>>
>
>
> -- 
> Nel mondo esistono 10 categorie di persone, quelle che capiscono il 
> binario e quelle che non lo capiscono.
>

-- 
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] Confirmed! GAE scheduler is stealing computing hours/money.

[Tapir]

On Monday, January 27, 2014 4:01:06 AM UTC+8, Tapir wrote:
>
>
>
> On Sunday, January 26, 2014 1:02:19 AM UTC+8, Tapir wrote:
>>
>>
>>
>> On Saturday, January 25, 2014 1:45:47 PM UTC+8, Vinny P wrote:
>>>
>>> On Fri, Jan 24, 2014 at 8:43 PM, Tapir  wrote:
>>>
 Before converting my app to modules style, the total front instance 
 hours were always less than 28 hours.

>>>
>>>
>>>
>>> If you still have a copy of your app before you converted to modules, 
>>> try uploading it and checking the performance. But this is most likely not 
>>> the fault of the modules service: App Engine seems to be encountering a lot 
>>> of "slowtime" this week, and you'll probably find that the errors smooth 
>>> themselves out sooner or later.
>>>
>>
>> Aha, I just checked the log, the datastore reading was really slow. A 
>> 1-second request speed 1 minute in the past 24 hours.
>>
>
> Aha again, there are about 300 such requests every day, so it is about 300 
> more minutes are spent on datastore reading.
> I think this is the really reason why my app's front end hours went up in 
> the past a few days.
>

Today, it seems all become normal again. In the past 12 hours, my app's 
frontend instance hours is 13.48 Instance Hours. So all days's hours would 
be about 27 hours, less than 28 again.
 

>  
>
>>  
>>
>>>   
>>>  
>>> -
>>> -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] app engine to work in Eclipse needed 1,7 jre what to do?

[Vinny P]

If you mean whether the Android SDK works with 7, yes it should:
http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Using-sourceCompatibility-1.7

-
-Vinny P
Technology & Media Advisor
Chicago, IL

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




On Sun, Jan 26, 2014 at 1:49 PM, Leonidas Savvides wrote:

> android should work with 7? basically all should fixed?
>
>
> On Mon, Jan 20, 2014 at 10:13 PM, Vinny P  wrote:
>
>> On Mon, Jan 20, 2014 at 7:23 AM, LWDLSE  wrote:
>>
>> app engine to work in Eclipse needed 1,7 jre what to do? I went to Pref >
>>> Jave > installed jre > jre and choose 1.7 (7) but same error appear
>>>
>>
>>
>> Uninstall all of the Java JRE and JDK installations on your computer
>> (including 6 and 7), and then reinstall JDK 7. Map Eclipse to use the fresh
>> install of 7.
>>
>>
>> -
>> -Vinny P
>> Technology & Media Advisor
>> Chicago, IL
>>
>> App Engine Code Samples: http://www.learntogoogleit.com
>>
>>  --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/google-appengine/6WB0BBmRTwo/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, 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.
>>
>
>  --
> 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.
>

-- 
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] Cache headers modified by Google Frontend

[Francois Masurel]

Hi Vinny,

Thanx for trying to help, I really appreciate what you do in this group.

The cache problem seems related to the fact that I'm connected on the site 
as an adminstrator.

In incognito mode or connected with another "basic" account, it works fine, 
resources are properly cached.

Connected with an "admin" account, caching seems to be disabled, at least 
on Chrome and Firefox.

Anybody could confirm such behavior?

Thanx again for your help.

François


On Sunday, January 26, 2014 8:23:43 PM UTC+1, Vinny P wrote:
>
> Hi Francois,
>
> As Nicolas said in this post: 
> https://groups.google.com/forum/#!topic/google-appengine/k3LrZodr-WA the 
> caching seems to be working correctly. I can see the proper Cache-Control 
> and Pragma headers in the response when I use Chrome's Developer Tools 
> screen. Are you still experiencing errors?
>
> If you're still seeing errors on your end, try this tool: 
> http://www.hurl.it/?url=http://dev.pronocities.com/theme/com.pronocities.theme.base/858/logo_mail.png(Press
>  the Launch Request button when the page loads). You'll be able to 
> see the response headers that Hurl.it gets back from the request.
>
>
>  
>  
> -
> -Vinny P
> Technology & Media Advisor
> Chicago, IL
>
> App Engine Code Samples: http://www.learntogoogleit.com
>   
>  
>
>
> On Sat, Jan 25, 2014 at 11:26 AM, Francois Masurel 
> 
> > wrote:
>
>> Hi everybody,
>>
>> Do you know why cache headers are modified by Google Frontend servers?
>>
>> Google prohibits my dynamically served static resources to be cached on 
>> proxy and user sides.
>>
>> For example, Google set the Expires header to this:
>> Expires: Fri, 01 Jan 1990 00:00:00 GMT
>>
>> And Pragma and Cache-Control to this:
>> Pragma: no-cache
>> Cache-Control: no-cache, must-revalidate 
>>
>> In my code, both Pragma and Cache-Control are set to public (plus max-age 
>> for Cache-Control).
>>
>> Example of problematic resource:
>>
>> http://dev.pronocities.com/theme/com.pronocities.theme.base/858/logo_mail.png
>>
>> What is strange is that the same exact code works perfectly fine in other 
>> apps like this one:
>>
>> http://www.vinocities.com/theme/com.vinocities.theme.base/858/logo_mail.png
>>
>> Anybody knows what's going on? What can I do to fix it?
>>
>> Thanx for your help.
>>
>> François
>>
>> -- 
>> 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-appengi...@googlegroups.com .
>> To post to this group, send email to 
>> google-a...@googlegroups.com
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>

-- 
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] Re: User facing requests going into the warm up instances and getting served

[Aswath Satrasala]

There is no traffic.  There is one instance running.  I issued a new
request.  A new instance is started and served.

Appengine team, please help us to avoid this or provide your guidelines, so
that a new instance is not started for a user facing request

Thanks
-Aswath


On Fri, Jan 10, 2014 at 10:49 PM, Vinny P  wrote:

> On Friday, January 10, 2014 7:58:54 AM UTC-6, Ian Marshall wrote:
>
>> You could increase your pending latency settings to the maximum allowed,
>> in order to try to have your app wait as long as possible for an existing
>> app instance to serve a web request. I use:
>>
>>   
>> 1
>> automatic
>> 15.0s
>> automatic
>> [...]
>>   
>>
>> to implement this, but I still get web requests being directed to a new
>> app instance which has just been launched and therefore is not ready to
>> serve immediately.
>>
>>>
>>>
>
> +1.
>
> The suggestions above are all good ideas, but regardless of the settings
> you choose there are always going to be some requests that initiate
> instance startup. How many requests (as a percentage of all requests) are
> causing instance startup in your application?
>
> In my experience, whenever App Engine gets more aggressive in starting up
> instances means that there's a new version of App Engine coming out. That
> or someone at Google is tinkering with the scheduler :-).
>
> -
> -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.