Re: [google-appengine] Full Text Search Storage

[Amy Unruh]

hi Sumit,

In the admin console, under 'Quota Details', you can get info about your
Search API calls and Search stored data.
If you click on 'Text Search' in the console, you can see a list of your
Search indexes and view the documents in them.

Currently there's no way to programmatically get info about the size of
your indexes (though you can list your indexes via the API).
Please file a feature request here:
  http://code.google.com/p/googleappengine/issues/list
if that's something you'd like to see.

 -Amy


On 9 July 2012 16:56, Sumit Kapoor  wrote:

> Hi,
>
> I had create two indexes under two different namespace (one index per
> namespace). Under each index I then added hundreds of documents. I was able
> to see the storage size for Full Test Search under the quota details page
> of my application console getting consumed, but I couldn't find away to
> access the documents and indexes from the console. Also the output of the
> stats API remained same.
>
> I used hooks while adding the documents and was able to get the document
> size then, but Is there a way to view and figure out the storage size of
> the documents that have already been added to an index ?
>
> Also is there a way to get the storage size of an index or all the indexes
> under a namespace using an API like stats ?
>
>  --
> 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/-/DIO9Th5G9MkJ.
> 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: Early access to Page Speed Service for Google App Engine

[Anders]

You really need to fix the slow cold starts of GAE apps. It can take 10 
seconds to load a webpage that usually loads in a fraction of a second. See 
issue:  http://code.google.com/p/googleappengine/issues/detail?id=7833 This 
seems 
to me something suitable for the Google Page Speed team to look into. The 
slow page load problem has come and gone for years for GAE.

On Wednesday, March 21, 2012 11:31:50 AM UTC+1, Ikai Lan (Google) wrote:
>
> Hey App Engine developers,
>
> We’re working on a new feature to help out your front-end development 
> efforts. We’ve been working with the Google Page Speed team (
> https://developers.google.com/pagespeed/service) to bring Page Speed 
> Service to your App Engine applications. When enabled, this feature will 
> analyze and rewrite pages served from your App Engine app such that they 
> load and render faster. A non-exhaustive list of some of the actions this 
> feature will automatically take care of are:
>
> - Compressing and minifying JavaScript
> - Serving static content off geographically disperse edge caches
> - Minimizing browser HTTP round trips
> - Minimizing payload size by optimizing images, rewriting CSS, etc. 
> - Optimize browser rendering by deferring JavaScript, image inlining, etc.
>
> The full list of rewriters provided by the page speed service can be found 
> here: 
> https://developers.google.com/speed/docs/pss/rewriters
>
> A quick analysis of some of the top App Engine applications demonstrated 
> an average render time improvement of 20%, though completely unoptimized 
> sites may experience a far more drastic impact. 
>  
> This sort of optimization is possible manually, though I’ve personally 
> found it to be fairly time consuming. We’re hoping this feature will help 
> developers launch faster so you can focus on building features instead of 
> tuning.
>
> You can sign up for early access to the feature here:
>
>
> https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dEZQbjVwc2RuMXFjZ0RUTWtUY25SMWc6MQ
>
> We’ll start inviting waves of developers into the program March 26, 2012. 
> You’ll get access to a tool that’ll allow you to compare performance 
> optimized and unoptimized versions of your pages side by side, turning on 
> and off the service as needed. We’re very interesting in hearing your 
> feedback.
>
> Cheers,
>
> - Ikai
>

-- 
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/-/nTCdTcWUrqUJ.
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: Instance startup time is *really* out of control

[Raymond Cidad]

Yes! finally. 
it was crazy lazy all day until like 15 min ago
not only starting, but putting and getting from the datastore.
ray

On Monday, July 9, 2012 10:06:18 PM UTC-4, Jeff Schnitzer wrote:
>
> It seems to have settled down. 
>
> Jeff 
>
> On Mon, Jul 9, 2012 at 7:04 PM, Amy Unruh  wrote: 
> > Jeff, Petey, and Jon, 
> > 
> > Are you still seeing this issue now? 
> > 
> > 
> > On 10 July 2012 08:04, Jon Stevens  wrote: 
> >> 
> >> I just saw a deploy which usually goes in about 1.5 minutes take 2.5 
> >> minutes... 
> >> 
> >> jon 
> >> 
> >> 
> >> On Monday, July 9, 2012 2:56:28 PM UTC-7, Jeff Schnitzer wrote: 
> >>> 
> >>> This problem is still ongoing.  F4 instances can't get off the ground. 
> >>> 
> >>> One instance startup attempt from a cron task (longer deadline) took 
> >>> 265 seconds before "The process handling this request unexpectedly 
> >>> died." 
> >>> 
> >>> Jeff 
> >>> 
> >>> On Mon, Jul 9, 2012 at 12:37 PM, Petey  wrote: 
> >>> > We are seeing the same thing. We are also getting Deadline Exceeded 
> >>> > errors 
> >>> > on just import libaries. 
> >>> > 
> >>> > 
> >>> > On Monday, July 9, 2012 11:35:27 AM UTC-7, Jeff Schnitzer wrote: 
> >>> >> 
> >>> >> Something is broken in GAE. 
> >>> >> 
> >>> >> No code changes.  Our production app startup time is now >60s and 
> >>> >> experiencing downtime periods.  Switching from F1 to F4 has no 
> effect, 
> >>> >> it still takes ~60s to start. 
> >>> >> 
> >>> >> This code takes 10s to start with an F4 in our sandbox environment. 
> >>> >> It does no eager loading. 
> >>> >> 
> >>> >> We've filed a production issue.  Appid is voost0. 
> >>> >> 
> >>> >> Jeff 
> >>> > 
> >>> > -- 
> >>> > 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/-/XdxXxZ5Vsj4J. 
> >>> > 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 view this discussion on the web visit 
> >> https://groups.google.com/d/msg/google-appengine/-/Co9nE-1jeJ0J. 
> >> 
> >> 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. 
>

-- 
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/-/qTepj07hDqQJ.
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: Instance startup time is *really* out of control

[Raymond Cidad]

We are getting a big delay requesting data from the server. like 
almost impossible to use the application delays. 
why is this not being displayed in the app engine status? 
any news? 

On Monday, July 9, 2012 3:37:54 PM UTC-4, Petey wrote:
>
> We are seeing the same thing. We are also getting Deadline Exceeded errors 
> on just import libaries.
>
> On Monday, July 9, 2012 11:35:27 AM UTC-7, Jeff Schnitzer wrote:
>>
>> Something is broken in GAE. 
>>
>> No code changes.  Our production app startup time is now >60s and 
>> experiencing downtime periods.  Switching from F1 to F4 has no effect, 
>> it still takes ~60s to start. 
>>
>> This code takes 10s to start with an F4 in our sandbox environment. 
>> It does no eager loading. 
>>
>> We've filed a production issue.  Appid is voost0. 
>>
>> Jeff 
>>
>

-- 
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/-/rWjbMB1ufvQJ.
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] deploying the App Engine: I just can seem to do it!

[Boy Lenssen]

I have been trying all day to get something running with App Engine. I use 
the Google plugin. I generate the cloud endpoints. 
Running it locally and addressing it via curl, no problems...

Then I deploy it, use the registered application id on appspot and go to: 
.appspot.com/_ah/api/discovery/v1/apis//v1/rest, and it 
says : Not found!

I was following this video until 20 minutes, 
http://www.youtube.com/watch?v=v9TG7OzsZqQ and did the above again, but 
still..the same...

what am I doing wrong...do I need to change a setting on appspot?

-- 
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/-/4Fu02n47IZoJ.
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] 上传gae yaml怎么写

[Miller]

urls.py:
('^$', 'siteWithResources.default.default'),  
( r'^js/(?P.*)$', 'django.views.static.serve',
{ 'document_root': 
'C:/Python25/Lib/site-packages/django/django-resources/js/' }
),
default.py(主程序)
   def default( request ):   
return render_to_response( 'django-templates/default.html',
{"mytitle":"bb"})
default.py的下级目录templates下有一个default.html网页

我写的app.yaml
application: mrqunying
version: 1
runtime: python
api_version: 1
skip_files: |
 ^(.*/)?(
 (app\.yaml)|
 (app\.yml)|
 (index\.yaml)|
 (index\.yml)|
 (#.*#)|
 (.*~)|
 (.*\.py[co])|
 (.*/RCS/.*)|
 (\..*)|
 (.*/\.svn/.*)|
 (.*/Thumbs\.db)|
 )$

handlers:

- url: /django-templates/default\.html
  script: default.py

- url: /.*
  script: default.py
  secure: optional
请问，app.yaml 的 handlers 如何写才能发布应用程序 ? 
本地测试是正常的。 
上传后显示：
The server encountered an error and could not complete your request.

-- 
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/-/21h2gjRgXg0J.
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] Full Text Search Storage

[Sumit Kapoor]

Hi,

I had create two indexes under two different namespace (one index per 
namespace). Under each index I then added hundreds of documents. I was able 
to see the storage size for Full Test Search under the quota details page 
of my application console getting consumed, but I couldn't find away to 
access the documents and indexes from the console. Also the output of the 
stats API remained same.

I used hooks while adding the documents and was able to get the document 
size then, but Is there a way to view and figure out the storage size of 
the documents that have already been added to an index ?

Also is there a way to get the storage size of an index or all the indexes 
under a namespace using an API like stats ?

-- 
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/-/DIO9Th5G9MkJ.
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] Bounding box spatial queries

[Amy Unruh]

On 10 July 2012 05:09, Jeff Schnitzer  wrote:

> On Mon, Jul 9, 2012 at 9:08 AM, John Patterson 
> wrote:
> > The new Full Text Search API allows a "find within X meters" type search
> but
> > I need a bounding box search.  Are there plans to implement this?
>
> I would like to know this as well.
>

We've created an external feature request for this; please star it if it's
of interest.
http://code.google.com/p/googleappengine/issues/detail?id=7834

  -Amy


>
> I would also like to know how price and performance will compare
> between search-geopt and using geohashing in the datastore.
>
> 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.
>
>

-- 
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] Need help or consulting: Request was aborted errors

[Kyle Finley]

Jeff, Thanks for the clarification. It's good to know that this is a free 
quota issue. The fact that the errors are not reported in the logs, makes 
it difficult to diagnose.

-- 
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/-/LE6uvPsseWMJ.
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] Need help or consulting: Request was aborted errors

[Jeff Schnitzer]

This is something different.  There is no "max instances" setting -
it's "max idle instances".  GAE will still spin up as many instances
as it deems necessary to meet demand... right up until you exhaust
quota.

FWIW, the paid scheduler does seem to operate considerably better than
the free scheduler.  For reasons I don't quite understand, free apps
seem to be pretty much unusable.  Enabling billing creates a much
smoother experience.

Jeff

On Mon, Jul 9, 2012 at 9:19 PM, Kyle Finley  wrote:
> I'm seeing the same thing with the test app I created. Even though I had max 
> instances set to 1 the scheduler still started up a second instance. During 
> this time I had several request that resulted in 500 server errors. Once the 
> second instance was started latency increased - as if the scheduler couldn't 
> decide which instance to route the request to. After a few seconds it 
> subsisted. I believe that this transition period maybe responsible for error 
> rates. The bad thing about it is:
>
> 1) The errors didn't appear in the logs.  So it is quite likely that this is 
> a common problem, but few developers are aware of it.
> 2) There's nothing that can be done to fix it.
>
> In fairness I was testing under the free quota, so maybe the scheduler 
> behaves better on payed apps.
>
> On Jul 9, 2012, at 10:05 PM, Richard wrote:
>
>> Ok, so I sat with Jeff in a G+ hangout for a while tonight, and we could not 
>> figure it out - other than my app is confusing the crap out of the scheduler 
>> which is then not sending requests to instances.
>
> --
> 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.
>

-- 
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] Need help or consulting: Request was aborted errors

[Kyle Finley]

I'm seeing the same thing with the test app I created. Even though I had max 
instances set to 1 the scheduler still started up a second instance. During 
this time I had several request that resulted in 500 server errors. Once the 
second instance was started latency increased - as if the scheduler couldn't 
decide which instance to route the request to. After a few seconds it 
subsisted. I believe that this transition period maybe responsible for error 
rates. The bad thing about it is:

1) The errors didn't appear in the logs.  So it is quite likely that this is a 
common problem, but few developers are aware of it.
2) There's nothing that can be done to fix it.

In fairness I was testing under the free quota, so maybe the scheduler behaves 
better on payed apps.

On Jul 9, 2012, at 10:05 PM, Richard wrote:

> Ok, so I sat with Jeff in a G+ hangout for a while tonight, and we could not 
> figure it out - other than my app is confusing the crap out of the scheduler 
> which is then not sending requests to instances.

-- 
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] Need help or consulting: Request was aborted errors

[Richard]

Ok, so I sat with Jeff in a G+ hangout for a while tonight, and we could 
not figure it out - other than my app is confusing the crap out of the 
scheduler which is then not sending requests to instances.



-- 
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/-/zrcGvBRcwlMJ.
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: Instance startup time is *really* out of control

[Jeff Schnitzer]

It seems to have settled down.

Jeff

On Mon, Jul 9, 2012 at 7:04 PM, Amy Unruh  wrote:
> Jeff, Petey, and Jon,
>
> Are you still seeing this issue now?
>
>
> On 10 July 2012 08:04, Jon Stevens  wrote:
>>
>> I just saw a deploy which usually goes in about 1.5 minutes take 2.5
>> minutes...
>>
>> jon
>>
>>
>> On Monday, July 9, 2012 2:56:28 PM UTC-7, Jeff Schnitzer wrote:
>>>
>>> This problem is still ongoing.  F4 instances can't get off the ground.
>>>
>>> One instance startup attempt from a cron task (longer deadline) took
>>> 265 seconds before "The process handling this request unexpectedly
>>> died."
>>>
>>> Jeff
>>>
>>> On Mon, Jul 9, 2012 at 12:37 PM, Petey  wrote:
>>> > We are seeing the same thing. We are also getting Deadline Exceeded
>>> > errors
>>> > on just import libaries.
>>> >
>>> >
>>> > On Monday, July 9, 2012 11:35:27 AM UTC-7, Jeff Schnitzer wrote:
>>> >>
>>> >> Something is broken in GAE.
>>> >>
>>> >> No code changes.  Our production app startup time is now >60s and
>>> >> experiencing downtime periods.  Switching from F1 to F4 has no effect,
>>> >> it still takes ~60s to start.
>>> >>
>>> >> This code takes 10s to start with an F4 in our sandbox environment.
>>> >> It does no eager loading.
>>> >>
>>> >> We've filed a production issue.  Appid is voost0.
>>> >>
>>> >> Jeff
>>> >
>>> > --
>>> > 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/-/XdxXxZ5Vsj4J.
>>> > 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 view this discussion on the web visit
>> https://groups.google.com/d/msg/google-appengine/-/Co9nE-1jeJ0J.
>>
>> 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.

-- 
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: Instance startup time is *really* out of control

[Amy Unruh]

Jeff, Petey, and Jon,

Are you still seeing this issue now?

On 10 July 2012 08:04, Jon Stevens  wrote:

> I just saw a deploy which usually goes in about 1.5 minutes take 2.5
> minutes...
>
> jon
>
>
> On Monday, July 9, 2012 2:56:28 PM UTC-7, Jeff Schnitzer wrote:
>>
>> This problem is still ongoing.  F4 instances can't get off the ground.
>>
>> One instance startup attempt from a cron task (longer deadline) took
>> 265 seconds before "The process handling this request unexpectedly
>> died."
>>
>> Jeff
>>
>> On Mon, Jul 9, 2012 at 12:37 PM, Petey  wrote:
>> > We are seeing the same thing. We are also getting Deadline Exceeded
>> errors
>> > on just import libaries.
>> >
>> >
>> > On Monday, July 9, 2012 11:35:27 AM UTC-7, Jeff Schnitzer wrote:
>> >>
>> >> Something is broken in GAE.
>> >>
>> >> No code changes.  Our production app startup time is now >60s and
>> >> experiencing downtime periods.  Switching from F1 to F4 has no effect,
>> >> it still takes ~60s to start.
>> >>
>> >> This code takes 10s to start with an F4 in our sandbox environment.
>> >> It does no eager loading.
>> >>
>> >> We've filed a production issue.  Appid is voost0.
>> >>
>> >> Jeff
>> >
>> > --
>> > 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/-/**XdxXxZ5Vsj4J.
>>
>> > To post to this group, send email to google-appengine@googlegroups.**
>> com .
>> > To unsubscribe from this group, send email to
>> > google-appengine+unsubscribe@**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 view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/Co9nE-1jeJ0J.
>
> 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: "Endpoints" section in the control panel?

[timh]

Does that mean that the tools exist to generate the client libs from 
annotated python code exist as well ?

T

On Tuesday, July 10, 2012 8:25:31 AM UTC+8, Dan Holevoet wrote:
>
> Google Cloud Endpoints supports Python as well. We don't have any specific 
> plans yet for supporting Go.
>
> Thanks,
> Dan
>
>
> On Fri, Jul 6, 2012 at 8:48 PM, timh  wrote:
>
>> HI
>>
>> I have watched all of the presentations/videos on endpoints.  All 
>> examples are java based.
>>  Are the tools and this service focussed on java only ?  What about 
>> python/go ?
>>
>> Cheers
>>
>> T
>>
>>
>> On Saturday, July 7, 2012 9:34:19 AM UTC+8, Amy Unruh wrote:
>>>
>>>
>>>
>>> On 3 July 2012 05:41, Tom Muse  wrote:
>>>
 Do you have the link for the video handy? I am having difficulties 
 locating it.
>>>
>>>
>>> Here's the I/O session video: https://developers.**
>>> google.com/events/io/sessions/**gooio2012/303/.
>>>
>>>  -Amy
>>>  
>>>

 Thanks in advance :)


 On Friday, June 29, 2012 6:50:45 PM UTC-4, Tom wrote:
>
> Just watched the video - endpoints look great.
>
> Are you able to give us some idea when they will be available for 
> non-Trusted testers?
>
> Thanks.
> Tom
>
> On Thursday, June 28, 2012 12:44:58 AM UTC-4, Christina Ilvento wrote:
>>
>> Hi All,
>>
>> Endpoints is one of the features we announced in our App Engine 
>> overview session today at I/O that's designed to make writing mobile 
>> backends on App Engine easier. More details to come in talks tomorrow 
>> (YouTube videos should be up soon) and we'll post some info with the 
>> trusted tester sign-up form to the groups shortly.
>>
>>
>> Thanks,
>> Christina
>>
>> On Wed, Jun 27, 2012 at 8:58 PM, James Broberg wrote:
>>
>>> I'd also like to know. Don't hold out on us now :)
>>>
>>>
>>> On 28 June 2012 06:45, Sam G  wrote:
>>>
 Bump. Any word from a Googler on what this is!?


 On Tuesday, June 26, 2012 4:59:33 PM UTC-7, Sam G wrote:
>
>
> This section just showed up for me in the App Engine dashboard.
> I also heard PageSpeed and SSL have been released? Where can I get 
> to these so that I can sign up?
>
> The new "Endpoints" section says that an API.yaml should exist... 
> what will go in that? Is there documentation up, now that this is a 
> production release?
>
>
> 
> Is this part of an I/O release?
>
> Screenshot sample attached.
>
  -- 
 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/**ms**g/google-appengine/-/**cA8hVE9iY*
 *pcJ
 .
  
 To post to this group, send email to google-appengine@googlegroups.
 com .
 To unsubscribe from this group, send email to 
 google-appengine+unsubscribe@**g**ooglegroups.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+unsubscribe@**g**ooglegroups.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 view this discussion on the web visit https://groups.google.com/d/**
 msg/google-appengine/-/**qC8lh4Gfn8gJ
 .

 To post to this group, send email to google-appengine@googlegroups.**
 com .
 To unsubscribe from this group, send email to 
 google-appengine+unsubscribe@**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 view this discussion on the web visi

[google-appengine] App Engine Office Hours hangout, 4pm PDT, Wed. 11th July

[Amy Unruh]

hi all,

We will have an App Engine office hours G+ hangout on this Wed., 11th July,
at 4pm Pacific time (23:00 UTC, 9:00 Thu in Sydney, 8:00 in Tokyo :).
We'll do a review of the Cloud-related news from Google I/O, and have time
for general discussion/questions.

Visit this event to find the link to the hangout when it starts up:

https://developers.google.com/live/shows/ahNzfmdvb2dsZS1kZXZlbG9wZXJzcg4LEgVFdmVudBjOu4UDDA/
Submit questions via Google Moderator:
  https://www.google.com/moderator/#15/e=1faeac&t=1faeac.43

 -Amy

-- 
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: "Endpoints" section in the control panel?

[Dan Holevoet]

Google Cloud Endpoints supports Python as well. We don't have any specific
plans yet for supporting Go.

Thanks,
Dan


On Fri, Jul 6, 2012 at 8:48 PM, timh  wrote:

> HI
>
> I have watched all of the presentations/videos on endpoints.  All examples
> are java based.
> Are the tools and this service focussed on java only ?  What about
> python/go ?
>
> Cheers
>
> T
>
>
> On Saturday, July 7, 2012 9:34:19 AM UTC+8, Amy Unruh wrote:
>>
>>
>>
>> On 3 July 2012 05:41, Tom Muse  wrote:
>>
>>> Do you have the link for the video handy? I am having difficulties
>>> locating it.
>>
>>
>> Here's the I/O session video: https://developers.**
>> google.com/events/io/sessions/**gooio2012/303/.
>>
>>  -Amy
>>
>>
>>>
>>> Thanks in advance :)
>>>
>>>
>>> On Friday, June 29, 2012 6:50:45 PM UTC-4, Tom wrote:

 Just watched the video - endpoints look great.

 Are you able to give us some idea when they will be available for
 non-Trusted testers?

 Thanks.
 Tom

 On Thursday, June 28, 2012 12:44:58 AM UTC-4, Christina Ilvento wrote:
>
> Hi All,
>
> Endpoints is one of the features we announced in our App Engine
> overview session today at I/O that's designed to make writing mobile
> backends on App Engine easier. More details to come in talks tomorrow
> (YouTube videos should be up soon) and we'll post some info with the
> trusted tester sign-up form to the groups shortly.
>
>
> Thanks,
> Christina
>
> On Wed, Jun 27, 2012 at 8:58 PM, James Broberg wrote:
>
>> I'd also like to know. Don't hold out on us now :)
>>
>>
>> On 28 June 2012 06:45, Sam G  wrote:
>>
>>> Bump. Any word from a Googler on what this is!?
>>>
>>>
>>> On Tuesday, June 26, 2012 4:59:33 PM UTC-7, Sam G wrote:


 This section just showed up for me in the App Engine dashboard.
 I also heard PageSpeed and SSL have been released? Where can I get
 to these so that I can sign up?

 The new "Endpoints" section says that an API.yaml should exist...
 what will go in that? Is there documentation up, now that this is a
 production release?


 
 Is this part of an I/O release?

 Screenshot sample attached.

>>>  --
>>> 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/**ms**g/google-appengine/-/**cA8hVE9iY**
>>> pcJ
>>> .
>>>
>>> To post to this group, send email to google-appengine@googlegroups.*
>>> ***com .
>>> To unsubscribe from this group, send email to
>>> google-appengine+unsubscribe@**g**ooglegroups.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+unsubscribe@**g**ooglegroups.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 view this discussion on the web visit https://groups.google.com/d/**
>>> msg/google-appengine/-/**qC8lh4Gfn8gJ
>>> .
>>>
>>> To post to this group, send email to 
>>> google-appengine@googlegroups.**com
>>> .
>>> To unsubscribe from this group, send email to
>>> google-appengine+unsubscribe@**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 view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/buKREK4jKSwJ.
>
> 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.
>



-- 
Dan Ho

[google-appengine] Re: Will we be able to buy discounted instance-hours for B1 backends?

[David Hardwick]

Here's the feature request here...

http://code.google.com/p/googleappengine/issues/detail?id=7411

On Jul 1, 2:31 pm, Robert Fischer  wrote:
> Hi,
>
> It's been some time since this post and I've been wondering the same thing.
>  Are there any plans to apply purchased discounted hours toward B1 (or
> other B#) instance hours?
>
> Thanks,
> Robert
>
>
>
>
>
>
>
> On Friday, September 16, 2011 2:54:47 PM UTC-7, Greg D'Alesandre wrote:
>
> > We don't plan to provide it just yet but could do so in the future.
>
> > Greg
>
> > On Fri, Sep 16, 2011 at 1:14 PM, Jason Collins 
> > wrote:
>
> >> The B1 backend specs are the same as frontend specs.
>
> >> Will we be able to buy discounted instance-hours for backend B1
> >> instances?
>
> >> Any possibility of a similar discount being applied to B2/B3/B4 for
> >> pre-commitment?
>
> >> j
>
> >> --
> >> 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.
>
> On Friday, September 16, 2011 2:54:47 PM UTC-7, Greg D'Alesandre wrote:
>
> > We don't plan to provide it just yet but could do so in the future.
>
> > Greg
>
> > On Fri, Sep 16, 2011 at 1:14 PM, Jason Collins 
> > wrote:
>
> >> The B1 backend specs are the same as frontend specs.
>
> >> Will we be able to buy discounted instance-hours for backend B1
> >> instances?
>
> >> Any possibility of a similar discount being applied to B2/B3/B4 for
> >> pre-commitment?
>
> >> j
>
> >> --
> >> 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.
>
> On Friday, September 16, 2011 2:54:47 PM UTC-7, Greg D'Alesandre wrote:
>
> > We don't plan to provide it just yet but could do so in the future.
>
> > Greg
>
> > On Fri, Sep 16, 2011 at 1:14 PM, Jason Collins 
> > wrote:
>
> >> The B1 backend specs are the same as frontend specs.
>
> >> Will we be able to buy discounted instance-hours for backend B1
> >> instances?
>
> >> Any possibility of a similar discount being applied to B2/B3/B4 for
> >> pre-commitment?
>
> >> j
>
> >> --
> >> 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.
>
> On Friday, September 16, 2011 2:54:47 PM UTC-7, Greg D'Alesandre wrote:
>
> > We don't plan to provide it just yet but could do so in the future.
>
> > Greg
>
> > On Fri, Sep 16, 2011 at 1:14 PM, Jason Collins 
> > wrote:
>
> >> The B1 backend specs are the same as frontend specs.
>
> >> Will we be able to buy discounted instance-hours for backend B1
> >> instances?
>
> >> Any possibility of a similar discount being applied to B2/B3/B4 for
> >> pre-commitment?
>
> >> j
>
> >> --
> >> 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.
>
> On Friday, September 16, 2011 2:54:47 PM UTC-7, Greg D'Alesandre wrote:
>
> > We don't plan to provide it just yet but could do so in the future.
>
> > Greg
>
> > On Fri, Sep 16, 2011 at 1:14 PM, Jason Collins 
> > wrote:
>
> >> The B1 backend specs are the same as frontend specs.
>
> >> Will we be able to buy discounted instance-hours for backend B1
> >> instances?
>
> >> Any possibility of a similar discount being applied to B2/B3/B4 for
> >> pre-commitment?
>
> >> j
>
> >> --
> >> 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.
>
> On Friday, September 16, 2011 2:54:47 PM UTC-7, Greg D'Alesandre wrote:
>
> > We don't plan to provide it just yet but could do so in the future.
>
> > Greg
>
> > On Fri, Sep 16, 2011 at 1:14 PM, Jason Collins 
> > wrote:
>
> >>

Re: [google-appengine] Re: Instance startup time is *really* out of control

[Jon Stevens]

I just saw a deploy which usually goes in about 1.5 minutes take 2.5 
minutes...

jon


On Monday, July 9, 2012 2:56:28 PM UTC-7, Jeff Schnitzer wrote:
>
> This problem is still ongoing.  F4 instances can't get off the ground. 
>
> One instance startup attempt from a cron task (longer deadline) took 
> 265 seconds before "The process handling this request unexpectedly 
> died." 
>
> Jeff 
>
> On Mon, Jul 9, 2012 at 12:37 PM, Petey  wrote: 
> > We are seeing the same thing. We are also getting Deadline Exceeded 
> errors 
> > on just import libaries. 
> > 
> > 
> > On Monday, July 9, 2012 11:35:27 AM UTC-7, Jeff Schnitzer wrote: 
> >> 
> >> Something is broken in GAE. 
> >> 
> >> No code changes.  Our production app startup time is now >60s and 
> >> experiencing downtime periods.  Switching from F1 to F4 has no effect, 
> >> it still takes ~60s to start. 
> >> 
> >> This code takes 10s to start with an F4 in our sandbox environment. 
> >> It does no eager loading. 
> >> 
> >> We've filed a production issue.  Appid is voost0. 
> >> 
> >> Jeff 
> > 
> > -- 
> > 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/-/XdxXxZ5Vsj4J. 
> > 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 view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/Co9nE-1jeJ0J.
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: Instance startup time is *really* out of control

[Jeff Schnitzer]

This problem is still ongoing.  F4 instances can't get off the ground.

One instance startup attempt from a cron task (longer deadline) took
265 seconds before "The process handling this request unexpectedly
died."

Jeff

On Mon, Jul 9, 2012 at 12:37 PM, Petey  wrote:
> We are seeing the same thing. We are also getting Deadline Exceeded errors
> on just import libaries.
>
>
> On Monday, July 9, 2012 11:35:27 AM UTC-7, Jeff Schnitzer wrote:
>>
>> Something is broken in GAE.
>>
>> No code changes.  Our production app startup time is now >60s and
>> experiencing downtime periods.  Switching from F1 to F4 has no effect,
>> it still takes ~60s to start.
>>
>> This code takes 10s to start with an F4 in our sandbox environment.
>> It does no eager loading.
>>
>> We've filed a production issue.  Appid is voost0.
>>
>> Jeff
>
> --
> 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/-/XdxXxZ5Vsj4J.
> 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] Need help or consulting: Request was aborted errors

[Kyle Finley]

I'm not sure why memcache would have stale data. Maybe a datastore query is 
some how responsable. The hrd is only strongly consistent when querying by 
key. 

As for Go, if I'm going to evangelize I should probably back it up. I put 
together a sample app to demonstrate it's concurrence. 

*Interface:* http://goscore.scotch-media.appspot.com/
*Source:* https://github.com/scotch/goscore/blob/master/server/http.go
*Leader Board JSON:* http://goscore.scotch-media.appspot.com/leaders

The Go runtime uses 
goroutines to 
handle request. So in theory it should be able to handle 1000's of 
request/second. I would be interested to see if this holds true on a 500Mhz 
virtual box.

Feel free to DDOS the *Leader Board 
JSON
 URL* I have the app set to 1 instance - so any latency will be from 1 
instance handling all of the request. If you are still seeing the "Request 
was aborted" then App Engine must have some type of throttle in place.

- Kyle

On Sunday, July 8, 2012 8:19:04 PM UTC-5, Richard wrote:
>
> I could if memcache actually worked.  But it does not.  I originally tried 
> to use it and found that I could not push the game state to memcache and 
> then have the other instances pull it.  They would get versions of it that 
> were up to 5 minutes old.  My timings are 5 second windows.
> 5 secs to submit all scores
> 5 secs to reap scores and calc leaderboards
> 5 secs to fan out results to clients
>
> Experience shows that memcache is just broken for that sort of timing.
>
> As for using Go instead of Python.  I am not sure I follow why Go should 
> be better.  The lag is not coming from CPU or queries.
>
> Right now I am running 50 instances to serve 500 game clients. $48 for the 
> last 18 hours.  11% of my requests result in "Request was aborted".  Yeah, 
> that is 12 THOUSAND fails.
>
> Back in the year 1995, ftp.cdrom.com could serve 2000 clients 
> simultaneously on a Pentium Pro 200MHz  and I cannot serve 20 clients 
> on a 500Mhz virtual box ?  
>
> I still contend there is some internal throttling going on somewhere.
>
> -R
>
>
>
> On Sunday, July 8, 2012 6:23:02 PM UTC-4, Kyle Finley wrote:
>>
>> Richard,
>>
>> Another option would be to move the Game State request to a 
>> Go instance, 
>> either as a 
>> backendor 
>> as a separate version. I believe a single Go instance should be able the 
>> handle 500 request / second. You could then share the Game State between 
>> the Python version and the Go version through Memcache, cacheing to 
>> instance memory every 5 sec. 
>>
>> - Kyle 
>>
>

-- 
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/-/PFW42x1I0M0J.
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: Transactions and queries in python app engine

[Guido van Rossum]

On Monday, July 9, 2012 4:28:30 PM UTC+2, pdknsk wrote:
>
> I don't know if it's documented, but it was mentioned in the release 
> notes. 
>
> The Datastore API now includes a NonTransactional decorator to ensure 
> that a function is run outside of a transaction. Existing transactions 
> are paused while the function is executing.


Also, in NDB you can run multiple transactions as well as non-transactional 
code "concurrently" using the propagation option to transaction() or 
@transactional(), or the @non_transactional decorator. (I put 
"concurrently" in parentheses since this is not a multi-threading API but 
simply uses NDB's async I/O facilities.)

See the docs 
at https://developers.google.com/appengine/docs/python/ndb/transactions 
(which sadly misspell this flag as "propogation". I will fix this.)

-- 
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/-/9zRp-2R_EaYJ.
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: Instance startup time is *really* out of control

[Petey]

We are seeing the same thing. We are also getting Deadline Exceeded errors 
on just import libaries.

On Monday, July 9, 2012 11:35:27 AM UTC-7, Jeff Schnitzer wrote:
>
> Something is broken in GAE. 
>
> No code changes.  Our production app startup time is now >60s and 
> experiencing downtime periods.  Switching from F1 to F4 has no effect, 
> it still takes ~60s to start. 
>
> This code takes 10s to start with an F4 in our sandbox environment. 
> It does no eager loading. 
>
> We've filed a production issue.  Appid is voost0. 
>
> Jeff 
>

-- 
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/-/XdxXxZ5Vsj4J.
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] Bounding box spatial queries

[Jeff Schnitzer]

On Mon, Jul 9, 2012 at 9:08 AM, John Patterson  wrote:
> The new Full Text Search API allows a "find within X meters" type search but
> I need a bounding box search.  Are there plans to implement this?

I would like to know this as well.

I would also like to know how price and performance will compare
between search-geopt and using geohashing in the datastore.

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: "Endpoints" section in the control panel?

[Amy Unruh]

On 1 July 2012 15:52, Vignesh Sundaresan  wrote:

> Very excited about Endpoints, Is it available yet for the trusted testers
> ??


For those interested in Trusted Tester access for Endpoints, you can fill
out this form:
http://endpoints-trusted-tester.appspot.com/


>
>
> On Wednesday, June 27, 2012 5:29:33 AM UTC+5:30, Sam G wrote:
>>
>>
>> This section just showed up for me in the App Engine dashboard.
>> I also heard PageSpeed and SSL have been released? Where can I get to
>> these so that I can sign up?
>>
>> The new "Endpoints" section says that an API.yaml should exist... what
>> will go in that? Is there documentation up, now that this is a production
>> release?
>>
>>
>> 
>> Is this part of an I/O release?
>>
>> Screenshot sample attached.
>>
>  --
> 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/-/HbBQ6RsyFeAJ.
>
> 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] Instance startup time is *really* out of control

[Jeff Schnitzer]

Something is broken in GAE.

No code changes.  Our production app startup time is now >60s and
experiencing downtime periods.  Switching from F1 to F4 has no effect,
it still takes ~60s to start.

This code takes 10s to start with an F4 in our sandbox environment.
It does no eager loading.

We've filed a production issue.  Appid is voost0.

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.

[google-appengine] Re: Memcache errors break session-saving. Should fail silently IMO. Any workaround?

[Per]

Hi Joakim,

replacing the session with a cookie is unfortunately not an option for us, 
our web framework stores a lot of stuff in the session.

I don't even want to use memcache at all, the session ends up in the 
datastore anyway, so if I had a choice, I would disable memcache here. It's 
just built that way in GAE.  I'd do anything to stop our users from  
getting 500-errors, and I'd like a way to ignore memcache errors here. 

I read that the sessions get stored into memcache namespace "_ahs", so I 
tried to register a LogAndContinue-Errorhandler for that namespace, but 
unfortunately that doesn't work either, at least not this way:


MemcacheServiceFactory.getMemcacheService("_ahs").setErrorHandler(new 
LogAndContinueErrorHandler(Level.INFO) {
@Override
public void handleDeserializationError(InvalidValueException 
thrown) {
log.error("gotcha!",thrown);
super.handleDeserializationError(thrown);
}

@Override
public void handleServiceError(MemcacheServiceException thrown) 
{
log.error("gotcha!",thrown);
super.handleServiceError(thrown);
}
});


Any idea how else to register a handler to prevent this from killing our 
requests?

Cheers,
Per





On Friday, July 6, 2012 7:24:26 PM UTC+2, Joakim wrote:
>
> If silent failure on write is to be acceptable, we need a way to make sure 
> following requests do not read session from memcache, as it could return an 
> old value. I am unaware of any way to accomplish this reliably without 
> hitting the datastore, at which point you might as well not have the 
> session in memcache at all.
>
> One possible alternative is to replace the entire session with storing 
> encrypted data in a cookie, though this only works for smaller amounts of 
> data as the maximum size for an entire cookie is generally said to be 4095 
> bytes.
>
> Just my 2 cents.
> Joakim
>
> On Wednesday, July 4, 2012 11:38:34 PM UTC+2, Per wrote:
>>
>>
>> When using sessions, these are (also) stored in memcache  by GAE. 
>> Unfortunately, it seems like any memcache hiccup can crash the process, 
>> turning an otherwise fine page into a 500 page on the way out.
>>
>> To me that looks like a design flaw. After all, Memcache is optional, and 
>> its expected to be unavailable or breaking every now and then. As of 1.6 
>> you can even provide a policy to silently ignore memcache errors inside 
>> your application. We're using 
>> setErrorHandler(ErrorHandlers.getConsistentLogAndContinue(Level.SEVERE)) 
>> with Objectify just fine, but it doesn't seem to have any effect on the 
>> Session-Save process. This seems to be entirely outside our control. 
>>
>> These errors are really annoying some of our clients. Is there maybe some 
>> kind of other error handler I'm missing?
>>
>> Here's the stracktrace for reference:
>>
>>
>> com.google.appengine.api.memcache.MemcacheServiceException: Memcache put: 
>> Error setting single item (_ahsOH7nik8bCRTbIXblKurKQQ)
>>  at 
>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:426)
>>  at 
>> com.google.appengine.api.memcache.AsyncMemcacheServiceImpl$7.transform(AsyncMemcacheServiceImpl.java:418)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$RpcResponseHandler.convertResponse(MemcacheServiceApiHelper.java:60)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:112)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceApiHelper$1.wrap(MemcacheServiceApiHelper.java:105)
>>  at 
>> com.google.appengine.api.utils.FutureWrapper.wrapAndCache(FutureWrapper.java:57)
>>  at 
>> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:98)
>>  at 
>> com.google.appengine.api.utils.FutureWrapper.get(FutureWrapper.java:90)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceImpl.quietGet(MemcacheServiceImpl.java:28)
>>  at 
>> com.google.appengine.api.memcache.MemcacheServiceImpl.put(MemcacheServiceImpl.java:81)
>>  at 
>> com.google.apphosting.runtime.jetty.MemcacheSessionStore.saveSession(MemcacheSessionStore.java:39)
>>  at 
>> com.google.apphosting.runtime.jetty.SessionManager$AppEngineSession.save(SessionManager.java:164)
>>  at 
>> com.google.apphosting.runtime.jetty.SaveSessionFilter.doFilter(SaveSessionFilter.java:41)
>>  at 
>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
>>  at 
>> com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:43)
>>  at 
>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
>>  at 
>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
>>  at 
>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>>   

Re: [google-appengine] Need help or consulting: Request was aborted errors

[Jeff Schnitzer]

Did switching to F4 make a difference?

Are these requests startup requests?  (they will be noted in the logs
"app engine started a new process...")

Have you put a log message at the beginning and end of the requests to
check timing?  It would be good to know if the lag is in your code or
outside of your code.

You mentioned that your app is very bursty, with 500 users submitting
data in a 5s window.  What's the time period between submissions?

Jeff

On Sun, Jul 8, 2012 at 7:26 PM, Richard  wrote:
> Yep, I know about that.  The internal limit is 1000msec, but you should aim
> for 750msec just to 'be safe'.
>
> Here are my timings:
>
> ms=15376 cpu_ms=37 api_cpu_ms=17 cpm_usd=0.003428 pending_ms=8265
>
> 37 msec of CPU  after waiting 8.2 seconds to execute.
>
> Some math:
>  - 500 incoming requests
>  - 40 servers
>  = ~ 15 requests/server
>  ... but each request takes ~55 msec of CPU + API 
>
> That's 825 msec for THE WHOLE LOT !   So why on earth is there 8 second
> of waiting before that request was serviced ?
>
>
> -R
>
>
> On Sunday, July 8, 2012 10:13:28 PM UTC-4, Per wrote:
>>
>>
>> Not sure where I saw it, but I believe an application must respond within
>> a second at most *on average*, or GAE reserves the right to throttle it. So,
>> if you have some kind of slowdown inside your app, then requests start
>> piling up. I'm not a Python developer, but if you had the equivalent of a
>> synchronised map in there, with lots of concurrent access, then you might
>> end up in a situation like this. Not sure about what's really to blame of
>> course, but I'd strongly recommend setting up a controlled loadtesting
>> environment (just copy the app, and start firing requests at it).  Add
>> plenty of logging to your app, enable appstats, and then slowly increase the
>> load. Maybe even strip the application down, starting only with read access.
>> I'm sure you will find something, and I would love to hear what it was! I
>> wish you luck!
>>
>>
>>
>>
>>
>> On Monday, July 9, 2012 3:19:04 AM UTC+2, Richard wrote:
>>>
>>> I could if memcache actually worked.  But it does not.  I originally
>>> tried to use it and found that I could not push the game state to memcache
>>> and then have the other instances pull it.  They would get versions of it
>>> that were up to 5 minutes old.  My timings are 5 second windows.
>>> 5 secs to submit all scores
>>> 5 secs to reap scores and calc leaderboards
>>> 5 secs to fan out results to clients
>>>
>>> Experience shows that memcache is just broken for that sort of timing.
>>>
>>> As for using Go instead of Python.  I am not sure I follow why Go should
>>> be better.  The lag is not coming from CPU or queries.
>>>
>>> Right now I am running 50 instances to serve 500 game clients. $48 for
>>> the last 18 hours.  11% of my requests result in "Request was aborted".
>>> Yeah, that is 12 THOUSAND fails.
>>>
>>> Back in the year 1995, ftp.cdrom.com could serve 2000 clients
>>> simultaneously on a Pentium Pro 200MHz  and I cannot serve 20 clients on
>>> a 500Mhz virtual box ?
>>>
>>> I still contend there is some internal throttling going on somewhere.
>>>
>>> -R
>>>
>>>
>>>
>>> On Sunday, July 8, 2012 6:23:02 PM UTC-4, Kyle Finley wrote:

 Richard,

 Another option would be to move the Game State request to a Go instance,
 either as a backend or as a separate version. I believe a single Go 
 instance
 should be able the handle 500 request / second. You could then share the
 Game State between the Python version and the Go version through Memcache,
 cacheing to instance memory every 5 sec.

 - Kyle
>
> --
> 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/-/J0pwVLK7RoEJ.
>
> 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] Bounding box spatial queries

[John Patterson]

The new Full Text Search API allows a "find within X meters" type search 
but I need a bounding box search.  Are there plans to implement this?

-- 
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/-/8NRFJlDHJ90J.
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] JDO Keys-only query counts toward Datastore Read instead of Datastore Small

[András Belicza]

When running Keys-only JDO queries, it is counted toward the "Datastore 
Entity Fetch Ops" instead of "Datastore Key Fetch Ops".

Example:
pm.newQuery( "select key from " + entityClass.getName() + " where date>:1" 
).execute( fromDate );

If there are 1000 entities meeting the criteria, the query will return a 
list having 1000 Keys (not entities). I would expect "Datastore Key Fetch 
Ops" to be increased by 1000, but instead it stays 0 and "Datastore Entity 
Fetch Ops" is increased by 1000 (+1 for the query).

This is crucial since Datastore read ops cost 0.7$/Million Ops and 
Datastore small Ops cost 0.1$/Million Ops.

Am I doing something wrong?

If I run the same query using the low level datastore API 
(DatastoreService), it is counted toward the Small Ops properly.

-- 
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/-/34RtkARNCucJ.
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: Transactions and queries in python app engine

[pdknsk]

I don't know if it's documented, but it was mentioned in the release
notes.

The Datastore API now includes a NonTransactional decorator to ensure
that a function is run outside of a transaction. Existing transactions
are paused while the function is executing.

-- 
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] Transactions and queries in python app engine

[FastGeert]

Hi,

is it possible to perform non-transactional datastore queries from inside a 
transaction?

In the java version of appengine, it is possible, but as far as I read in 
the python documentation, I don't think it is possible in the python 
version of appengine.


-- 
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/-/dgfh9TAi9ugJ.
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] Cannot create a new application

[Ray]

Hi, 

I have 2 problems. First I registered a domain last year through google 
appengine and entered my credit card details and checked that google 
automatically charge me for the next domain renewal. but I got an email two 
months ago from domainsbyproxy.com saying that your domain name is on sale 
and you can buy that from us. I first thought that's a fake email but when 
I check the whois I found they acctually own the domain. My bank account 
was/is correct because google is charging me for the appengine's services 
(bandwith, process...).  I tried to contact Godaddy and google butno luck. 
My question is can I get my domain back or can I rely on google to register 
another domain with them?

My another problem is I cannot create any more application on google 
appengine. It doesn't show any error message. The application just doesn't 
appear on the applications's list. I still should be able to create 6 
application. 

Thanks in advance for your help

Ray

-- 
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/-/Wp54qMjD9NEJ.
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: Get namespace

[timh]

Think about it,

If you do 

bla = namespace_manager.get_namespace()
namespace_manager.set_namespace(bla)


Then you have just fetched the current namespace, and then set it to that value.

Setting the namespace needs to be done with every request.


Have a look at the first few paragraphs of Setting the  Current Namespace in

 https://developers.google.com/appengine/docs/python/multitenancy/multitenancy




T


On Thursday, July 5, 2012 10:19:03 PM UTC+8, vivendi wrote:
>
> I'm currently implementing the App Engine in a Python web app. But i'm 
> really stuck with a few things that, in my opinion, the documentation 
> doesn't really cover. Not in great detail anyway.
>
> First thing that i'm trying to do is get the current namespace, and then 
> set that namespace. This works good for me:
>
> namespace_manager.set_namespace('test')
>
> But for some reason the following doesn't work when i visit this URL:
> (fictive url) http://test.my-app.appspot.com
>
> bla = namespace_manager.get_namespace()
> namespace_manager.set_namespace(bla)
>
> This doesn't give me the namespace data, but just the data that was saved 
> under no namespace.
>
> Anyone any idea what the problem could be?
>
>
>

-- 
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/-/mD7IGpi0aLYJ.
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] Need help or consulting: Request was aborted errors

[timh]

Others have asked, and I will too have you profiled your app with appstats 
yet ?

A few other points,

have you compared the performance of multiple instances with threading off 
vs threading enabled ? 
Are you using warmup requests to startup new instances ?
I personally have never experienced out of date memcahce data.  Have you 
logged an issue with appengine team.  Getting 5min old stale date from 
memcache should never happen.
Finally python with threads isn't going to give you magical increases in 
concurrent throughput. If the request is cpu bound then other threads won't 
get a look in.  Where threading in requests works is when you request 
starts waiting on rpc's.  Then other work can be scheduled. 

T

On Monday, July 9, 2012 10:26:01 AM UTC+8, Richard wrote:
>
> Yep, I know about that.  The internal limit is 1000msec, but you should 
> aim for 750msec just to 'be safe'.
>
> Here are my timings:
>
> ms=15376 cpu_ms=37 api_cpu_ms=17 cpm_usd=0.003428 pending_ms=8265
>
> 37 msec of CPU  after waiting 8.2 seconds to execute.
>
> Some math:
>  - 500 incoming requests
>  - 40 servers
>  = ~ 15 requests/server
>  ... but each request takes ~55 msec of CPU + API  
>
> That's 825 msec for THE WHOLE LOT !   So why on earth is there 8 second 
> of waiting before that request was serviced ?
>
>
> -R
>
> On Sunday, July 8, 2012 10:13:28 PM UTC-4, Per wrote:
>>
>>
>> Not sure where I saw it, but I believe an application must respond within 
>> a second at most *on average*, or GAE reserves the right to throttle it. 
>> So, if you have some kind of slowdown inside your app, then requests start 
>> piling up. I'm not a Python developer, but if you had the equivalent of a 
>> synchronised map in there, with lots of concurrent access, then you might 
>> end up in a situation like this. Not sure about what's really to blame of 
>> course, but I'd strongly recommend setting up a controlled loadtesting 
>> environment (just copy the app, and start firing requests at it).  Add 
>> plenty of logging to your app, enable appstats, and then slowly increase 
>> the load. Maybe even strip the application down, starting only with read 
>> access. I'm sure you will find something, and I would love to hear what it 
>> was! I wish you luck!
>>
>>
>>
>>
>>
>> On Monday, July 9, 2012 3:19:04 AM UTC+2, Richard wrote:
>>>
>>> I could if memcache actually worked.  But it does not.  I originally 
>>> tried to use it and found that I could not push the game state to memcache 
>>> and then have the other instances pull it.  They would get versions of it 
>>> that were up to 5 minutes old.  My timings are 5 second windows.
>>> 5 secs to submit all scores
>>> 5 secs to reap scores and calc leaderboards
>>> 5 secs to fan out results to clients
>>>
>>> Experience shows that memcache is just broken for that sort of timing.
>>>
>>> As for using Go instead of Python.  I am not sure I follow why Go should 
>>> be better.  The lag is not coming from CPU or queries.
>>>
>>> Right now I am running 50 instances to serve 500 game clients. $48 for 
>>> the last 18 hours.  11% of my requests result in "Request was aborted".  
>>> Yeah, that is 12 THOUSAND fails.
>>>
>>> Back in the year 1995, ftp.cdrom.com could serve 2000 clients 
>>> simultaneously on a Pentium Pro 200MHz  and I cannot serve 20 clients 
>>> on a 500Mhz virtual box ?  
>>>
>>> I still contend there is some internal throttling going on somewhere.
>>>
>>> -R
>>>
>>>
>>>
>>> On Sunday, July 8, 2012 6:23:02 PM UTC-4, Kyle Finley wrote:

 Richard,

 Another option would be to move the Game State request to a 
 Go instance, 
 either as a 
 backendor 
 as a separate version. I believe a single Go instance should be able the 
 handle 500 request / second. You could then share the Game State between 
 the Python version and the Go version through Memcache, cacheing to 
 instance memory every 5 sec. 

 - Kyle 

>>>

-- 
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/-/ctfUY0KajbsJ.
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] Need help or consulting: Request was aborted errors

[Per]

It's obviously very hard to diagnose this remotely. But if it's spending 8 
out of 15 seconds waiting, then what about the other 7 seconds, where 
exactly are they lost? There's no point arguing that this should work (of 
course it should), IMO you need to start analysing. Maybe you did already, 
but it's not obvious from your posts what you did already, and what you 
didn't. In another thread you mentioned you didn't use appstats for a long 
time - I'd do that first thing. Also, I'd add very detailed manual logging, 
so you know what bits run fast, and which ones don't. 

I've encountered plenty of GAE glitches in the past, but also quite a few 
things were our own fault. I'm not sure how performance analysis works on 
Python, but in Java it would be time to bring on the good old Profiler. I'd 
make sure that on localhost a request really just takes a few miliseconds, 
even under load, and then take it live, to a loadtesting environment and 
see what happens there under growing load. Given the numbers you posted, 
I'd not be surprised if some locking&synchronizing is part of the problem, 
but that's just a guess. Find out what operation really takes the most 
time, or at what load things start going wrong. 


On Monday, July 9, 2012 4:26:01 AM UTC+2, Richard wrote:
>
> Yep, I know about that.  The internal limit is 1000msec, but you should 
> aim for 750msec just to 'be safe'.
>
> Here are my timings:
>
> ms=15376 cpu_ms=37 api_cpu_ms=17 cpm_usd=0.003428 pending_ms=8265
>
> 37 msec of CPU  after waiting 8.2 seconds to execute.
>
> Some math:
>  - 500 incoming requests
>  - 40 servers
>  = ~ 15 requests/server
>  ... but each request takes ~55 msec of CPU + API  
>
> That's 825 msec for THE WHOLE LOT !   So why on earth is there 8 second 
> of waiting before that request was serviced ?
>
>
> -R
>
> On Sunday, July 8, 2012 10:13:28 PM UTC-4, Per wrote:
>>
>>
>> Not sure where I saw it, but I believe an application must respond within 
>> a second at most *on average*, or GAE reserves the right to throttle it. 
>> So, if you have some kind of slowdown inside your app, then requests start 
>> piling up. I'm not a Python developer, but if you had the equivalent of a 
>> synchronised map in there, with lots of concurrent access, then you might 
>> end up in a situation like this. Not sure about what's really to blame of 
>> course, but I'd strongly recommend setting up a controlled loadtesting 
>> environment (just copy the app, and start firing requests at it).  Add 
>> plenty of logging to your app, enable appstats, and then slowly increase 
>> the load. Maybe even strip the application down, starting only with read 
>> access. I'm sure you will find something, and I would love to hear what it 
>> was! I wish you luck!
>>
>>
>>
>>
>>
>> On Monday, July 9, 2012 3:19:04 AM UTC+2, Richard wrote:
>>>
>>> I could if memcache actually worked.  But it does not.  I originally 
>>> tried to use it and found that I could not push the game state to memcache 
>>> and then have the other instances pull it.  They would get versions of it 
>>> that were up to 5 minutes old.  My timings are 5 second windows.
>>> 5 secs to submit all scores
>>> 5 secs to reap scores and calc leaderboards
>>> 5 secs to fan out results to clients
>>>
>>> Experience shows that memcache is just broken for that sort of timing.
>>>
>>> As for using Go instead of Python.  I am not sure I follow why Go should 
>>> be better.  The lag is not coming from CPU or queries.
>>>
>>> Right now I am running 50 instances to serve 500 game clients. $48 for 
>>> the last 18 hours.  11% of my requests result in "Request was aborted".  
>>> Yeah, that is 12 THOUSAND fails.
>>>
>>> Back in the year 1995, ftp.cdrom.com could serve 2000 clients 
>>> simultaneously on a Pentium Pro 200MHz  and I cannot serve 20 clients 
>>> on a 500Mhz virtual box ?  
>>>
>>> I still contend there is some internal throttling going on somewhere.
>>>
>>> -R
>>>
>>>
>>>
>>> On Sunday, July 8, 2012 6:23:02 PM UTC-4, Kyle Finley wrote:

 Richard,

 Another option would be to move the Game State request to a 
 Go instance, 
 either as a 
 backendor 
 as a separate version. I believe a single Go instance should be able the 
 handle 500 request / second. You could then share the Game State between 
 the Python version and the Go version through Memcache, cacheing to 
 instance memory every 5 sec. 

 - Kyle 

>>>

-- 
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/-/_V2FQCZb_sQJ.
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 option

[google-appengine] RuntimeHelper.checkRestricted adding 25X overhead to antlr parsing on GAE Java 1.7

[Marc Hacker]

We are using *antlr* parsing on GAE 1.7 and find a 25x overhead running on 
GAE v. standalone Java app because it spends 96% of its time in 
RuntimeHelper.checkRestricted()!!

(We are NOT in GAE 1.6.4 which had a bug of extra calls to 
RuntimeHelper.checkRestricted)

Does anyone know a list of which method calls trigger calls to 
RuntimeHelper.checkRestricted so that we can potentially avoid those 
please? For some reason I can't find any documentation of this security 
manager and what triggers it.

One call which repeatedly triggers a time-consuming call to checkRestricted 
seems to be antlr.runtime.DFA.predict(IntStream)

How can we avoid this impossibly big security overhead please - thanks!

Thanks!

-- 
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/-/yWpCiBYpl7AJ.
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.