[google-appengine] Re: Currently getting hundreds of 503 errors calling service from task queue

[bFlood]

we are getting lots of 500 "Request was aborted after waiting too long to 
attempt to service your request" (10sec) errors in area of our code that 
has worked for years. Some are from the task queue. It started about a week 
and half ago. Its sporadic, I can't figure out the pattern

On Thursday, July 23, 2020 at 9:17:25 AM UTC-4 Rob Curtis wrote:

> Hi, I'm suddenly getting hundreds of 503 errors when call task handler in 
> service.
>
> Is anyone else experiencing this outage?
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9570d878-9cfd-48c8-83f6-ba29cc4316e7n%40googlegroups.com.

Re: [google-appengine] Diving into App Engine is soooooooooooo hard now - My analysis

[bFlood]

Is there an official AppEngine Standard Python 2.7 depreciation date? the 
SDK (appcfg) is gone in July2020 but has anything been announced with 
regard to the runtime/hosting environment yet?

thanks. 


On Monday, March 23, 2020 at 11:54:50 AM UTC-4, Olu wrote:
>
> Thank you for your feedback, Alexey and I understand your concerns. I 
> however encourage you to use the issue tracker links for creation of 
> features[1] that you consider would be nice to have on GCP. The team are 
> committed to reviewing such requests and considering how these requests fit 
> into the GCP Road map. 
>
> Similarly, You could always submit issue links to request clarifications 
> and better explanations on particular GCP Documentations that you may be 
> using. These requests will be reviewed and forwarded to the Documentation 
> team who further review the details and provide the needed updates on the 
> Documentation page. 
>
> Our team are always looking for ways to make GCP products and its 
> documentation pages better. 
>
> Thank you for your understanding. 
>
> [1]https://cloud.google.com/support/docs/issue-trackers#feature_requests
> [2]https://cloud.google.com/support/docs/issue-trackers#trackers-list
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/dcb49298-797e-4484-86a2-5603f6affa02%40googlegroups.com.

[google-appengine] Custom Domains - P2 - High Impact - Service Severely Impaired

[bFlood]

we have a "P2 - High Impact - Service Severely Impaired" issue right now 
and its been 2.5 hours since we've heard from Google Support on the case. 
is there anyway to elevate an issue? We spend tens of thousands every year 
on GCP

 We've been using AppEngine since it started and have changed ssl 
certificates several times, this time something went wrong in the process 
and we're only half working. all www traffic is 404, never reaches our 
instances

for the first time, I'm starting to have major doubts about where the whole 
Google Cloud Platform is heading

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/865f0fd6-6438-46b7-9c04-c9b21fedc7fc%40googlegroups.com.

[google-appengine] Re: Migrating GAE app stored user information to GAE Python 3.0 without Users API

[bFlood]

has anyone tried Firebase Authentication API as a suitable replacement for 
GAE Python 2.7 Users api?
https://firebase.google.com/docs/auth/

this doc lays it out nicely:
https://cloud.google.com/appengine/docs/standard/python/authenticating-users-firebase-appengine

also, it looks like you can have as many Firebase Authentication users as 
you need for free (eg public user of your app). can someone at google 
confirm this as well? I had thought Firebase was priced per user?

thank you


On Wednesday, February 20, 2019 at 8:10:54 PM UTC-5, davidc...@google.com 
wrote:
>
> Hello Marcel,
>
> We expect these IDs to be the same but cannot guarantee it. The best way 
> to confirm this is to try it in your test environment; store the user ID of 
> a user from an application using the Users API and then using the same user 
> try to access application using Google Identity Platform to compare these 
> IDs. 
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/39ee233a-fd53-423a-9197-f6caea4576f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE python 2.7 end of life

[bFlood]

its not the incompatibility of python (language/runtime), its missing 
services with regard to GAE Standard 2.7 and GAE Standard 3.0. (memcache, 
NDB, Search, Images, Users, webapp2, etc). Are these going to be duplicated 
in GAE3? and if so, will existing data and model definitions in the 2.7 
datastore work in 3? 

it looks like some work is being done for this but it would be great to 
know officially what Google plans for this upgrade process. how much code 
will need to change? 
https://github.com/googleapis/google-cloud-python/issues?q=NDB+sort%3Aupdated-desc

also, generally what do you mean by "not directly affected on an immediate 
time frame"? a year, 2 years, 5 years before 2.7 apps stop running? 




On Wednesday, January 9, 2019 at 9:32:36 AM UTC-5, George (Cloud Platform 
Support) wrote:
>
> You are perfectly right, NP. Python 3 is made incompatible with 2, and 
> Python 3 does not support quite a few features, and will require effort to 
> re-program your app in an alternative manner. I was simply saying that 
> often the effort is not enormous, and becomes worthwhile on the longer 
> term. 
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8f45b06f-0852-4e46-9331-c3ebdbe3e481%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE python 2.7 end of life

[bFlood]

google - please provide a roadmap for GAE 2.7 standard, what will happen to 
these apps? 
will they be required to upgrade to the python 3.0 (2nd generation 
runtimes)?
if so, can you address the significant differences listed here:
https://cloud.google.com/appengine/docs/standard/python3/python-differences

no memcache, no urlfetch, no users, no ndb, no local development? I'm 
assuming some of these will be fairly easy to replace (urlfetch) but what 
about upgrading ndb models to the cloud datastore? will it be automatic? 
what about the performance loss thats been reported in the issues forum?

there are lot of unanswered questions regarding GAE python 2.7 and 2020 is 
not that far away, please provide some guidance


On Tuesday, January 8, 2019 at 6:07:02 AM UTC-5, ajgomezlopez wrote:
>
> python 2.7 is no longer supported on January 1, 2020.
>
> What will happen to the applications in the standard environment?
> Is there a end of life date or something similar?
>
> thx.
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2e1d869a-0175-44b9-b11b-03ebe0b7fdd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google App Engine roadmap

[bFlood]

that article is from 2008 and the link does not point at a road-map, its 
just a description of the current standard offerings



On Friday, August 17, 2018 at 6:35:02 PM UTC-4, Katayoon (Cloud Platform 
Support) wrote:
>
> As mentioned in “Google App Engine Roadmap - Now Published 
> ”
>  
> article, App Engine road-map can be found here 
> .
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9648550c-9abb-4879-a013-c94f3f48a130%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Will Pipelines and MapReduce libraries work on Python 3.7?

[bFlood]

"More related detail can be gathered from the "Understanding differences 
between Python 2 and Python 3 on the App Engine standard environment" 
documentation page. "
https://cloud.google.com/appengine/docs/standard/python3/python-differences#cloud_client_libraries

based on that doc, I don't think a year will be enough?!? I think you owe 
it to many of your longtime GAE developers to produce both short term and 
long term roadmaps for the python2.7 runtime. will there be wrappers for 
all of the existing GAE services? (ndb, users, memcache etc)? if not, how 
long can we realistically expect 2.7 to be supported? 





On Friday, August 10, 2018 at 12:19:29 PM UTC-4, George (Cloud Platform 
Support) wrote:
>
> Hello Jacob, 
>
> It is difficult to predict such things as deprecation deadlines, as they 
> depend on various factors such as requests from Customers, market outlook, 
> actual needs and implementation of new features to replace the old. In any 
> case, you should not worry as long as no public announcement is made. In 
> all similar cases from the past, public announcements were made no less 
> than a year in advance, so you can be sure that Python 2.7 won't be 
> declared as obsolete before at least one year from now on; more precisely 
> at least one year from the date of the future announcement. These long 
> delays are offered for the precise reasons you mentioned: the substantial 
> effort to re-create and adapt your apps to the new environment. This 
> applies in a similar way to the various built-in services you refer to.  
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a1bb5dbb-691d-4914-8301-0f1b5860fa35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] AppEngine down? - 502 errors

[bFlood]

AppEngine down? - 502 errors 

anyone else? 

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b8826703-9c1e-4f85-925d-c75120174a31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Image Detection - I want it to look in my library (bucket) only and identify based on images in my own bucket

[bFlood]

only in alpha now but isn't this what AutoML is suppose to solve? (at least 
the photo based portion, they mentioned there will be other AutoML 
modules). You load your own images, label them and then use the Vision API 
to access the results

https://cloud.google.com/automl/



On Tuesday, February 20, 2018 at 6:55:18 AM UTC-5, barryhunter wrote:
>
> Technically no. You can't upload your own training dataset, and train the 
> AI to produce *your *labels. 
>
> Would need to deploy your own implementation - possibly via 
> https://opensource.google.com/projects/tensorflow - deployed on GCE
>
> https://www.tensorflow.org/tutorials/image_recognition
>
>
> https://cloud.google.com/solutions/running-distributed-tensorflow-on-compute-engine
>
>
>
> ... but have had reasonable success building a *second *layer on top of 
> the API, to produce custom labels. Not sure what the proper name is, some 
> sort of Meta-AI.
>
>
> Basically
>
> 1) Run all your existing images though the Cloud Vision API, and gather 
> the feature labels it produces. 
>
> 2) You now have a mapping of 'labels' to your own 'value' - although 
> somewhat fuzzy. Will have a long list of labels for each value. Store these 
> in a database
>
> 3) To 'search' images by your "value". first look at the image(s) with 
> that value, and gather all the labels. THen look for the images with the 
> most similar labels. 
>
> 4) Can also do 'vision lookup' by uploading a image to the Cloud Vision 
> API, and retrieveing a list of labels. Then search your database looking 
> for the images with the most 'similar' labels. Take the 'value from the 
> best match(es).
>
>
> It doesnt matter that what the labels Google AI is detecting on the 
> images, even if nothing like your 'values', just that they similar 
> 'looking'. Say you have a value of 'animal'. The vision api may detect 
> those images as a mixture of differnt animals (cow/dog etc), but you have a 
> mapping back and forth, via your 'training' dataset.  
>
> Not an AI expert, so probably messing up the terminology, but the labels 
> that Google's AI produces become almost like a set of hidden neurons on 
> your *final *Meta-AI
>
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/9638c9f7-63d8-457b-a047-4752054fb96b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: URGENT: is GAE Standard memcache down????

[bFlood]

agreed, memcache is down

On Monday, November 6, 2017 at 3:56:52 PM UTC-5, PK wrote:
>
> This started returning False 15 minutes ago. My app is down because of it. 
>
> from google.appengine.api.capabilities import CapabilitySet 
> print CapabilitySet('memcache', methods=['set']).is_enabled() 
>
>
>
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5d754de9-f3ea-427f-af4e-7acbcc6d759b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Process terminated because the request deadline was exceeded. (Error code 123)

[bFlood]

yea, its back working again now but that's a little disconcerting 
considering they closed the incident report earlier today

On Tuesday, May 17, 2016 at 11:50:30 AM UTC-4, Леонтьев Пётр wrote:
>
> We had small batch or errors too. It took roughly 5-10 minutes. 
>
> вторник, 17 мая 2016 г., 14:54:45 UTC+3 пользователь Мария Кокаия написал:
>>
>> All requests to the Google Cloud SQL are returning instant errors: 
>> "Process terminated because the request deadline was exceeded. (Error code 
>> 123)". We have only 1 active connection to Cloud SQL. We tried to restart 
>> SQL instance, no matter. It doesn't work
>>
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/370abba2-edd5-4800-9eda-a59914d856c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Process terminated because the request deadline was exceeded. (Error code 123)

[bFlood]

I'm seeing these errors again, did something else break?



On Tuesday, May 17, 2016 at 10:01:55 AM UTC-4, Nick (Cloud Platform 
Support) wrote:
>
> Hey Folks,
>
> Yes, this was indeed a platform issue. We'll have an incident report 
> posted here . 
>
> On Tuesday, May 17, 2016 at 9:24:08 AM UTC-4, Aditya Agarwalla wrote:
>>
>> Its back up. Here's the latest from the Status page of Google.
>>
>> On Tuesday, May 17, 2016 at 5:24:45 PM UTC+5:30, Мария Кокаия wrote:
>>>
>>> All requests to the Google Cloud SQL are returning instant errors: 
>>> "Process terminated because the request deadline was exceeded. (Error code 
>>> 123)". We have only 1 active connection to Cloud SQL. We tried to restart 
>>> SQL instance, no matter. It doesn't work
>>>
>>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4f80bdef-a8f8-433e-95c9-9fae40f882aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Process terminated because the request deadline was exceeded. (Error code 123)

[bFlood]

this is causing major headaches, anything google?

On Tuesday, May 17, 2016 at 8:04:18 AM UTC-4, Osman AKTAS wrote:
>
> I have same problem. what should i do . Please help :(
>
> 17 Mayıs 2016 Salı 14:54:45 UTC+3 tarihinde Мария Кокаия yazdı:
>>
>> All requests to the Google Cloud SQL are returning instant errors: 
>> "Process terminated because the request deadline was exceeded. (Error code 
>> 123)". We have only 1 active connection to Cloud SQL. We tried to restart 
>> SQL instance, no matter. It doesn't work
>>
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/5767b838-f8f1-40f9-a82e-1024d4daa31d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: New Cloud Console

[bFlood]

how do you search/filter on the new log viewer? does it require enabling 
Google Cloud Monitoring (which is still in beta)? 

On Tuesday, February 23, 2016 at 6:46:19 PM UTC-5, johnP wrote:
>
> Just got email that old appengine console will be shut off in 6 weeks. 
>  The new cloud console does not have a "migrate traffic" option in the 
> Versions screen.  This was my absolute favorite new feature in a long, long 
> time.  Will it be available in the new console?
>

-- 
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 https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/44321a90-3a1d-490c-a68f-96ce372b53c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Google APIs integrated authentication

[bFlood]

well its sorted out now but it was down for 8+ hours, that's pretty bad. is 
there a post mortem on the issue yet?

On Thursday, December 10, 2015 at 12:34:50 PM UTC-5, Nick (Cloud Platform 
Support) wrote:
>
> @Miguel, good to hear things are sorted out. 
>
> If any further issues are noticed by anybody, feel free to post them to 
> the relevant Public Issue Tracker forum, such as google-appengine [1], 
> googlecloudsql [2], google-cloud-sdk [3], or google-cloud-platform [4], 
> depending what's affected, with the last one being a safe catch-all.
>
> [1] https://code.google.com/p/google-appengine/issues/list
> [2] https://code.google.com/p/googlecloudsql/issues/list
> [3] https://code.google.com/p/google-cloud-sdk/issues/list
> [4] https://code.google.com/p/google-cloud-platform/issues/list
>
> On Wednesday, December 9, 2015 at 5:58:11 PM UTC-5, Miguel Vitorino wrote:
>>
>> Hi Nick,
>>
>> Yes, that's right, the issues were manifested as 401s across all APIs and 
>> were solved once incident #15025 was fixed.
>>
>> Miguel
>>
>> Miguel Vitorino
>>
>> Director
>> Skype: miguel.vitorino
>> Support UK: +44 (20) 33 896 112
>> Support US: +1 (646) 350-0511
>>
>>
>>
>> On 9 December 2015 at 20:46, Nick (Cloud Platform Support) <
>> pay...@google.com > wrote:
>>
>>> Were these errors manifesting as 401 responses? There's very little 
>>> description in this thread of what issues are actually being seen. Is 
>>> this <https://status.cloud.google.com/incident/appengine/15025> 
>>> possibly the issue you were affected by (linked to the Cloud Status 
>>> Dashboard)? The appengine-downtime-notify mailing list also saw a 
>>> posting <https://status.cloud.google.com/incident/appengine/15025> 
>>> about this.
>>>
>>>
>>> On Tuesday, December 8, 2015 at 4:02:57 PM UTC-5, Stefano Ciccarelli 
>>> wrote:
>>>>
>>>> Same here, our app is partially unusable (because it cannot reach GCS) 
>>>> but we have not been contacted. 
>>>>
>>>> Il giorno mar 8 dic 2015 alle 20:58 bFlood <bfl...@spatialdatalogic.com 
>>>> > ha scritto:
>>>>
>>>>> same here, we have not been contacted but our app is affected as well
>>>>>
>>>>>
>>>>> On Tuesday, December 8, 2015 at 2:53:18 PM UTC-5, Miguel Vitorino 
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Google Cloud Platform mailing list has just posted this announcement:
>>>>>>
>>>>>> "We’re investigating elevated error rates for some Google Cloud 
>>>>>> Platform users. We believe these errors are affecting between 2-5 
>>>>>> percent 
>>>>>> of Google App Engine (GAE) applications. We are working directly with 
>>>>>> the 
>>>>>> customers who are affected to restore full operation in their 
>>>>>> application 
>>>>>> as quickly as possible, and apologize for any inconvenience."
>>>>>>
>>>>>> Anyone know what exactly Google is doing directly with the affected 
>>>>>> customers. Our app is severely affected and we have received no contact 
>>>>>> or 
>>>>>> instructions regarding this.
>>>>>>
>>>>>> Miguel 
>>>>>>
>>>>> -- 
>>>>> 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.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/google-appengine/dbc0fe86-abe3-40fe-a112-b3d73974e90a%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/google-appengine/dbc0fe86-abe3-40fe-a112-b3d73974e90a%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> -- 
>>>> *Stefano Ciccarelli* 
>>>> GAE Application Division 
>>&

Re: [google-appengine] Google Cloud Storage - token Not accepted all of a sudden.

[bFlood]

Google says they are working with those who are affected by this, how do we 
get our name on that list? 

On Tuesday, December 8, 2015 at 2:31:07 PM UTC-5, Alex Martelli wrote:
>
> Looks like an effect of the incident being tracked at 
> https://status.cloud.google.com/incident/appengine/15025 .
>
> Alex
>
> On Tue, Dec 8, 2015 at 9:26 AM, Will Reiher  > wrote:
>
>> Nothing has changed since yesterday when uploading was working as 
>> expected. Today I'm seeing 401s and invalid token errors. App Engine to 
>> Cloud Storage with cloud storage.
>>
>> Connect with us at:
>> 
>>
>> *FriesenPress* | Suite 300 - 990 Fort St, Victoria, BC, Canada, V8V 3K2 
>> | *http://www.friesenpress.com * | 
>> *http://blog.friesenpress.com 
>> *
>>
>> You are receiving this email because you are a FriesenPress client or 
>> partner. This email and any documents attached to it may contain 
>> confidential information. If you are not the intended recipient, you are 
>> hereby notified that any disclosure, copying or distribution of the 
>> contents of this email is prohibited. If you no longer wish to receive 
>> promotional emails from FriesenPress visit 
>> *http://www.friesenpress.com/agreement/email/ 
>> * to change your settings.
>>
>> The privacy of your information is important to us. To learn more, visit 
>> our *privacy policy *.
>>
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/009b9f1b-9a67-44e5-8385-8126217b4738%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/d3f25e15-d621-4aeb-b7e2-d0a505a31c5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Google APIs integrated authentication

[bFlood]

same here, we have not been contacted but our app is affected as well


On Tuesday, December 8, 2015 at 2:53:18 PM UTC-5, Miguel Vitorino wrote:
>
>
> Hi,
>
> Google Cloud Platform mailing list has just posted this announcement:
>
> "We’re investigating elevated error rates for some Google Cloud Platform 
> users. We believe these errors are affecting between 2-5 percent of Google 
> App Engine (GAE) applications. We are working directly with the customers 
> who are affected to restore full operation in their application as quickly 
> as possible, and apologize for any inconvenience."
>
> Anyone know what exactly Google is doing directly with the affected 
> customers. Our app is severely affected and we have received no contact or 
> instructions regarding this.
>
> Miguel 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/dbc0fe86-abe3-40fe-a112-b3d73974e90a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Memory Usage Doubled in the Past 20 Hours or So

[bFlood]

i see the same thing, memory has doubled but traffic is identical. looks 
like it started at some time during 3/24/15



On Friday, March 20, 2015 at 6:25:13 PM UTC-4, Michael Sander wrote:

 This seems to be getting even worse I'm hitting 5GB of memory even though 
 my load is pretty tiny.


 https://lh4.googleusercontent.com/-27TrkW2v_ns/VQyeMtF5-hI/Cc8/Oar2yQzLCCw/s1600/2015-03-20%2BScreenshot%2B3.png



 On Friday, March 20, 2015 at 5:37:39 PM UTC-4, Michael Sander wrote:

 Totally uncorrelated. Traffic hasn't changed at all... actually it's 
 decreased a bit. Summary screenshot below.


 https://lh3.googleusercontent.com/-N0wvSx7XKY8/VQyTERNZCkI/Ccs/qlp7PyXsEBk/s1600/2015-03-20%2BScreenshot%2B2.png


 On Friday, March 20, 2015 at 5:31:41 PM UTC-4, Alex Martelli wrote:

 How have various measures of _traffic_ to your app been changing over 
 the last couple days?  I.e, is that doubling of memory quite uncorrelated 
 with an increase in traffic?

 Alex

 On Fri, Mar 20, 2015 at 2:27 PM, Michael Sander michael...@gmail.com 
 wrote:

 Did google upgrade or change something recently? About 20 hours ago my 
 app started consuming about twice as much memory as before. I have not 
 updated or changed my app at all in the past few days. See screenshot 
 below.


 https://lh6.googleusercontent.com/-RPylKvSjchA/VQyQrQiQKUI/Ccg/9pZJ54ZTFr0/s1600/2015-03-20%2BScreenshot.png

  -- 
 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.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/google-appengine/873c2e73-7087-43a3-9643-de3c4539f3b3%40googlegroups.com
  
 https://groups.google.com/d/msgid/google-appengine/873c2e73-7087-43a3-9643-de3c4539f3b3%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 For more options, visit https://groups.google.com/d/optout.




-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/6ebdaeb5-dee3-4ca1-ac57-82b442359550%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App deployment stuck and then failed with version not ready

[bFlood]

seeing the same thing across multiple apps

On Friday, September 26, 2014 12:57:23 PM UTC-4, Markus A. wrote:

 Getting frequent errors from the admin page (appengine.google.com) also:

 Error: Server ErrorThe server encountered an error and could not complete 
 your request.

 Please try again in 30 seconds.

 On Friday, September 26, 2014 9:54:28 AM UTC-7, Markus A. wrote:

 Same problem here right now...

 Also, the admin console is EXTREMELY slow...


 On Wednesday, September 12, 2012 8:05:28 PM UTC-7, gks wrote:

 I am unable to deploy to my apps in the past 20 hrs. All deployments 
 stuck at the stage of Verifying availability of frontend and eventually 
 failed with Version not ready.

 My AppIDs are aos-prod-1  aos-prod-2.

 Any help will be greatly appreciated!



-- 
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/d/optout.

[google-appengine] Re: High latencies over the last 12 or so hours

[bFlood]

seeing huge latency today

On Wednesday, April 9, 2014 5:23:44 AM UTC-4, timh wrote:

 Hi

 Has anyone noticed higher than normal latencies over the last 12 hours or 
 so.
 I normally see 1000ms mostly around 300-400ms,. but most requests today 
 are int he 3000-4000ms territory

 Cheers

 Tim


-- 
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/d/optout.

[google-appengine] Re: New Pricing

[bFlood]

Search API - did the price increase? simple/complex searches have been 
blended into one price that's closer to the old complex one (?)

On Tuesday, March 25, 2014 2:44:52 PM UTC-4, pdknsk wrote:

 The most significant changes I spotted.

 Instances hours base price is reduced from $0.08 to $0.05 now.
 Blobstore reduced from $0.13 to $0.026 am I reading this right?! Also 
 applies to Logs and Taskstore, both $0.24 previously.
 Dedicated Memcache price halved.
 Small datastore operations free!

 No MB increase for instances unfortunately.


-- 
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/d/optout.

[google-appengine] Re: 1.9.0 Pre-Release SDKs are now available.

[bFlood]

agreed, can someone please confirm this?

On Saturday, February 22, 2014 10:48:45 PM UTC-5, Kaan Soral wrote:

 So if I understood correctly, the 250GB index limit is now 10GB's?!
 (Again, if I understood correctly, the 10gb per unlimited indexes limit 
 seems a bit bullshity to me, as one could also have created multiple apps 
 to increase the total limit in that manner, as others have previously done 
 for other limits)

 I hope I misunderstood


-- 
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: HItting query limit using Geocoding API from App Engine

[bFlood]

how many requests are you making? the per IP limits are still pretty 
small...

On Tuesday, December 17, 2013 5:17:50 PM UTC-5, Jeremy McLain wrote:

 This is driving me crazy.  I've tried three different proxies and I am 
 still getting: You have exceeded your daily request quota for this API.


-- 
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: 250gb search index size limitation

[bFlood]

there's not much data in there right now, probably because each of my 
documents only has 10-15 fields. I'm wondering how much perf degrades as 
the indexes grow. I was hoping they didn't at all but jon's 3sec latency 
must be coming from somewhere

~200K documents over 3 indexes. doc size is variable but all pretty much 
below 1KB. 
Search API Bytes Indexed   0.01 GBytes
Search API Stored Data   0.11 of 250.00 GBytes

I'm using search docs to front end datastore entities with Json properties 
holding the bulk of non-indexed data. I'm also trying out search docs in 
front of simple json docs in Cloud Storage. Maybe this is different then 
other people's use of the search api since it's not very text intensive




-- 
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: 250gb search index size limitation

[bFlood]

hi jon

I'd be interested to know the size of your documents and the index itself. 
I guess mine are relatively small now (200K docs, 1kb each) but in 
production, the average search latency is around 200-300ms (haven't tested 
under significant load though). I've never seen 3 seconds for queries but 
maybe its just my data

cheers
brian

On Sunday, September 8, 2013 2:25:17 AM UTC-4, jon wrote:

 Oops sorry I missed the bit where you said you only used the SDK.

 I use snippet (bolding) to present Google-like search results. Being able 
 to see where documents match my search keywords makes a big difference.

 Yes, 3+ seconds is on production. My search results are returned via AJAX 
 too, and I personally find the delay long enough to be very annoying.

 I really want GAE FTS to be good, because I have 2 webapps that use it and 
 I don't want to waste time migrating search to an external service, but to 
 me FTS is sufficiently broken that I'll have to move away at some point. 
 More importantly, I suspect that FTS gets very little attention from 
 developers and Googlers alike. I mean, the 2 problems that I mentioned are 
 glaringly obvious, and yet no one raises it (as far as I know). If it takes 
 Googlers between 1-3 years to fix/introduce highly requested features, it 
 will take even longer to fix lightly used stuff like FTS.

 Here's hoping that a Googler responds to this thread and restores my 
 faith, but I'm not holding my breath :)

 On Saturday, September 7, 2013 8:01:27 PM UTC+10, Kaan Soral wrote:

 I've never tried the feature on production, as I stated I've been using 
 it on SDK, for a long while now
 Didn't try the bolding feature, wonder how it does the actual bolding and 
 how it can be of any use, since searchable stuff is generally seperate from 
 actual stuff and a manual bolding seems easier, if necessary, off topic

 Is 3+ seconds on production? If so, it indeed sounds extreme, however 3 
 seconds is better than nothing, since my search requests are from ajax, 3+ 
 seconds wouldn't be so irritating (in comparison, overhead of an external 
 search service might be closer to 3 seconds too, or at least ~500ms)

 *And the reason I think it's beyond-awesome*

 In theory it works, it fills an empty spot, there are no appengine 
 alternatives to it, the search is satisfactory
 Properties are great, syntax is easy and satisfactory, Document logic is 
 simple and well-thought, imo
 The query logic is similar to db/ndb, I'm using it the same way I'm using 
 ndb queries, the cursor system is similar, same handlers are responding to 
 ndb and search queries

 When I first started using search, deep inside I hoped that it isn't as 
 awesome as it seems, and it isn't, since it's obviously not scalable, as 
 it's limited, otherwise it might even beat datastore in terms of 
 indexing/querying

 + The ranking system is great, don't remember how I utilized it, however 
 my search results appear by their ndb importance metric

 Thinking about it right now, the beyond is an overkill, but it is 
 awesome, *hoping the limitations disappear really soon*

 On Saturday, September 7, 2013 12:31:49 PM UTC+3, jon wrote:


 however the search index size limitation will prevent any decent 
 use-case of this *beyond-awesome feature*


 May I ask why you think this is an awesome feature? I've been using FTS 
 for a while now and I find that:

- It's slow. It easily takes 3+ seconds to return search results.
- Result snippet (bolding matching text) is broken. Try searching 
with just one word, and you'll find no bolding occurs. If you use two 
words, only the second is bolded.



-- 
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] Re: Finding all the locations in a given radius with GQL

[bFlood]

the AppEngine SearchAPI has decent geo search support, just make sure to 
send lat/lon values with enough accuracy or the results may be off

Location-Based Queries (Geosearch) (near the bottom)
https://developers.google.com/appengine/training/fts_adv/lesson1

cheers
brian

-- 
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] Run Task on specific Module

[bFlood]

hello all

How do you target specific Modules from the Task queue? With Backends, it 
was a simple target param. Am I missing something obvious?

taskqueue.add(queue_name='backup', url=/tasks/backup, params=params, 
target=worker)

worker.yaml:
application: {{my_app_name}}
version: v1
runtime: python27
threadsafe: true
instance_class: B4_1G

-- 
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: Search quota

[bFlood]

yea, any word on this?

On Friday, May 31, 2013 1:58:51 AM UTC-4, Goran Popovic wrote:

 Any news on updating search quota?
 I mean, 3 years passed and we still have experimental quotas..

 Goran Popovic


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

[google-appengine] static files

[bFlood]

any one else having problems uploading new static files? older ones are 
serving fine, anything added today is not serving. works fine in dev 
environment

cheers
brian

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

[google-appengine] Re: static files

[bFlood]

nevermind, dumb error on my part

On Friday, May 31, 2013 1:48:40 PM UTC-4, bFlood wrote:

 any one else having problems uploading new static files? older ones are 
 serving fine, anything added today is not serving. works fine in dev 
 environment

 cheers
 brian


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

Re: [google-appengine] App Engine for Government?

[bFlood]

hi greg - can you contact me as well? any information on this would be very 
helpful as we are actively looking at cloud hosting for our municipal 
clients (US)

On Wednesday, November 2, 2011 7:17:06 PM UTC-4, Greg D'Alesandre wrote:

 Hi drtman, you've in essence contacted Google directly now :)  I'll 
 contact you offlist for more details.

 Greg D'Alesandre
 Senior Product Manager, Google App Engine

 On Wed, Nov 2, 2011 at 4:13 PM, drtman drt...@gmail.com javascript:wrote:

 I am considering hosting an application on GAE but in order to do so
 would need to provide the same terms that are used for Google Apps for
 Government.  Is there a way to do this with an App Engine app (i.e. an
 App Engine for Government)?  Also, I would need an SLA uptime
 guarantee of 99.99% or better and doesn't look like that is available
 on GAE. Do I need to look at other clouds?  I'd like to contact Google
 directly to discuss this but can't find a way to do so.

 --
 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-a...@googlegroups.comjavascript:
 .
 To unsubscribe from this group, send email to 
 google-appengi...@googlegroups.com javascript:.
 For more options, visit this group at 
 http://groups.google.com/group/google-appengine?hl=en.




-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To 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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[google-appengine] Re: AppEngine not serving - Error Code 121

[bFlood]

thanks for the links, starred them all. Not sure how I missed them before, 
thx

the issue seems to have taken care of itself, here the error graph now.

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


attachment: dashboard_2.png

[google-appengine] AppEngine not serving - Error Code 121

[bFlood]

one of my apps has gone haywire, it's been working well for over 2 years.

HRD
Nothing changed in code/settings etc
About 50-60% of the requests now show Error Code 121
This seemed to start about 7 hours ago
app-id: get-arc2earth-hrd


https://lh5.googleusercontent.com/-aZZ2UeqbbUI/USpyGEYizvI/AAM/rXBeIe9_MOw/s1600/dashboard.png

https://lh4.googleusercontent.com/-SkZ51_vrIbU/USpyItELHXI/AAU/AE50ZRPwlq0/s1600/instances.png

https://lh3.googleusercontent.com/-SuMhshw85G8/USpyKqpWDBI/AAc/dwxwjG21Mfg/s1600/logs.png
please help asap...


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

[google-appengine] Re: Funny spikes in graphs

[bFlood]

maybe it's ProdEagle itself, that hits your app every minute



On Jan 31, 10:16 am, Mike Wesner mike.wes...@webfilings.com wrote:
 Have you looked at the logs to see what/who is making the requests?
 It could be some type of polling or service that is making requests at
 those intervals.

 -Mike

 On Jan 31, 8:40 am, Andrin von Rechenberg and...@miumeet.com wrote:







  Hey there

  My dashboard shows funny spikes in all graphs (qps, bandwidth, ram).
  It's been doing this for a couple of days now. ProdEagle shows everything
  is fine, so I guess something must be messed up on Google's side...

  Anyone else seeing this?

  Cheers,
  -Andrin

   Screen shot 2012-01-31 at 3.38.39 PM.png
  56KViewDownload

-- 
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: Do you Serialize your Data?

[bFlood]

hi brandon

I do this with a bunch of models, keep a few properties for search and
then dump the bulk of data into a compressed, json text property.
Obviously the json part might be overkill but its a lot more flexible
going forward if (err, when) you need to add more data (especially
nested data)

reads and writes are faster, YMMV

YMMV
b

On Jan 17, 4:44 am, Brandon Wirtz drak...@digerat.com wrote:
 We are looking at restructuring some of our calls, optimizing again for
 speed, we are thinking that rather than having a datastore call for a single
 cell, we'd serialize things.

 This makes searching suck, and we have had a few issues where serialized and
 unserialized data didn't quite match when we were done (because of weird
 encoded characters from sites)

 Serializing also locks you in to a single data structure for the most part.

 We are also just considering:
 data as a zipped, delimited array
 uncompressed, delimited
 Double storing, so that we pay twice for writes, and can run analytics, but
 so that reads are against the serialized data, and faster and cost less.

 What are anyone's thoughts? Have you had these discussions with your dev
 team?

-- 
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: Do you Serialize your Data?

[bFlood]

hi brandon

compression - not really, at least not with HRD. I remember it being
useful in M/S but only for larger strings. I'm using this python
property now, it only compresses over a certain size
http://atastypixel.com/blog/wp-content/uploads/2011/01/compressible_text_property.py_.txt

great article jeff, I know I've read of few of your older posts about
this in the past

cheers
brian


On Jan 17, 9:21 am, Brandon Wirtz drak...@digerat.com wrote:
 You wrote How to Use GAE to Get Laid and didn't tell anyone?  Evil.







 -Original Message-
 From: google-appengine@googlegroups.com

 [mailto:google-appengine@googlegroups.com] On Behalf Of Jeff Schnitzer
 Sent: Tuesday, January 17, 2012 6:10 AM
 To: google-appengine@googlegroups.com
 Subject: Re: [google-appengine] Re: Do you Serialize your Data?

 In fact, I wrote up an explanation of this 6 months ago:

 http://blog.similarity.com/post/7541938593/how-to-build-an-online-dat...
 e-nosql-edition

 Jeff

 On Tue, Jan 17, 2012 at 2:06 PM, Jeff Schnitzer j...@infohazard.org wrote:
  I tend to do this a lot to minimize the cost of fetching data; if I
  need all the information about a Person then I get all that info by
  loading a single entity, usually pulled from memcache. Most of my
  analytic processes look like map/reduce so indexing these complex
  structures wouldn't really help.

  If you're in Javaland you can use Objectify4 and annotate a field with
  @Serialize(zip=true) to get it automatically compressed. I haven't
  compared resulting entity sizes, however.

  Jeff

  On Tue, Jan 17, 2012 at 1:27 PM, Brandon Wirtz drak...@digerat.com
 wrote:
  Have you weighed Compression vs uncompressed in terms of speed, and cost?

  I'll end up testing to see, but I like to know the answers beforehand
  :-)

  -Original Message-
  From: google-appengine@googlegroups.com
  [mailto:google-appengine@googlegroups.com] On Behalf Of bFlood
  Sent: Tuesday, January 17, 2012 4:54 AM
  To: Google App Engine
  Subject: [google-appengine] Re: Do you Serialize your Data?

  hi brandon

  I do this with a bunch of models, keep a few properties for search
  and then dump the bulk of data into a compressed, json text property.
  Obviously the json part might be overkill but its a lot more flexible
  going forward if (err, when) you need to add more data (especially
  nested data)

  reads and writes are faster, YMMV

  YMMV
  b

  On Jan 17, 4:44 am, Brandon Wirtz drak...@digerat.com wrote:
  We are looking at restructuring some of our calls, optimizing again
  for speed, we are thinking that rather than having a datastore call
  for a single cell, we'd serialize things.

  This makes searching suck, and we have had a few issues where
  serialized and unserialized data didn't quite match when we were
  done (because of weird encoded characters from sites)

  Serializing also locks you in to a single data structure for the
  most
  part.

  We are also just considering:
  data as a zipped, delimited array
  uncompressed, delimited
  Double storing, so that we pay twice for writes, and can run
  analytics, but so that reads are against the serialized data, and
  faster
  and cost less.

  What are anyone's thoughts? Have you had these discussions with your
  dev team?

  --
  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 
  athttp://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 
 athttp://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] HR Down?

[bFlood]

suddenly lots of The API call datastore_v3.Get() took too long to
respond and was cancelled and The API call user.CreateLoginURL()
took too long to respond and was cancelled errors

anyone else?

-- 
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: HR Down?

[bFlood]

seems to be back up now.

for the record, that was about 10-15 mins of nothing working.
Python27, threadsafe=false, HR

cheers
brian

On Jan 5, 10:31 am, bFlood bfl...@spatialdatalogic.com wrote:
 suddenly lots of The API call datastore_v3.Get() took too long to
 respond and was cancelled and The API call user.CreateLoginURL()
 took too long to respond and was cancelled errors

 anyone else?

-- 
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: Hosting Mapnik, TileStache in Google App Engine

[bFlood]

i think they are hosting the output from tilestache on GAE (just json
files). but I could be wrong

cheers
brian

On Dec 16, 10:21 am, Raj arthiyagara...@gmail.com wrote:
 Hi Brian,

 Thanks for your reply. Because, I am not a member I was not able to
 post any message. But, now I can :)

 So, in this case may be I have to host them in some good Linux Host.
 Although, I have seen people hosting Tilestache in GAE.

 -Thanks
 Raj

 On Nov 16, 8:57 pm, bFlood bfl...@spatialdatalogic.com wrote:







  hi raj

  You won't be able to get Mapnik to run, it definitely has some c
  runtime dependencies. As for TileStache, depending on what
  functionality you wanted, you might be able to get it running. but
  afaik, it uses OGR for data access, so that would be useless on GAE as
  well.

  all in all, I'm not sure you'll have much luck with either

  cheers
  brian

  On Nov 16, 11:13 am, Raj arthiyagara...@gmail.com wrote:

   Hey,

   Before using google app engine, I thought its not a bad idea to ask to
   wise people in this group.

   My basic requirement is to host,

   Mapnik (Mapnik is a Free Toolkit for developing mapping 
   applications,http://mapnik.org/),
   TileStache (TileStache is a Python-based server application that can
   serve up map tiles based on rendered geographic 
   data,http://tilestache.org/).
   Any direction/insight on this would be helpful.

   As I looked into the 'Google App Engine SDK for Python' : (Windows/Mac
   OS X/Linux/Other Platforms/MapReduce Bundle),
   I am trying to use the 'Linux app engine'(because my production
   environment is linux based). But my development environment is Windows
   based. So, does my download platform(OS) matters? or should I use the
   appropriate one for the respective environment(dev/prod)?

   -Thanks
   Raj

-- 
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: Isn't .08/hr 1.92/day $59.52/month for a 600 MHZ CPU instance with 128 MB memory a LITTLE EXPENSIVE

[bFlood]

exactly jeff, well put.

On Dec 14, 10:36 am, Jeff Schnitzer j...@infohazard.org wrote:
 I think there is a legitimate gripe here which is that large-memory
 instances are unreasonably expensive.

 There's some significant value-add for GAE's whole package -
 automatic scaling, memcache, edge caching, deployment system, API
 access (although these APIs are generally charged separately).  This
 makes the $60/mo for a basic (multithreaded) instance worthwhile.
 It's expensive but it's convenient, and most frontend work fits fine
 in the F1.  Also it's a little bit of apples/oranges because the GAE #
 is heap whereas an Amazon # is VM size, but this is probably less than
 a factor of 2 difference.

 On the other hand, there are many application components whose primary
 requirement is a significant chunk of RAM.  All that Google
 infrastructure is nice but it isn't nice enough to warrant a 10X
 premium just for a measly 1G of RAM.  And you can't even get more.
 Seriously, a cheap amazon standard instance has significantly more
 RAM than the most expensive GAE instance... lame.

 Consequently, backends are useful as a long-running frontend, but
 absolutely useless as an in-memory index.  We're priced into going the
 inconvenient route of placing memory indexes in other cloud services.

 I've been generally accepting of GAE's recent pricing changes, but the
 price of large-memory instances basically means I have to treat that
 option as if it doesn't exist.  Which means when Google adds all these
 fancy features to support different kinds of instances, from my
 perspective, they're wasting their time.  I can't use them until they
 make them cheaper.

 So here's my plea:  a 256MB instance shouldn't cost twice as much as a
 128MB instance, and a 512MB instance shouldn't cost twice as much as a
 256MB instance.  The price curve should drop off.  There's a
 reasonable premium to pay for running on GAE, but a factor of 10 isn't
 it.

 Just for comparison... the largest GAE backend, at 1G, costs $460/mo.
 A 1.5G linode instance costs $60/mo.  And I can get a 4G linode
 instance for $160/mo.  And while it's not exactly an apples/apples
 comparison, when I need RAM, the priority of all those other Google
 niceties goes down considerably.  And if I needed (say) four 1G
 backends, you can absolutely bet that I will go with Linode and pocket
 the extra $20k per year.

 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: DeadlineExceeded errors haunting every now and then

[bFlood]

using an HR app and getting sporadic DDE as well

The API call datastore_v3.Get() took too long to respond and was
cancelled.

so much for HR solving everything

and fwiw, I've also run up $100 in charges on an older M/S app (no
code changes in months) that gets maybe 1000 requests/day. Nearly
every other request is a DDE

On Dec 7, 10:04 pm, daniel_ge_smith daniel.ge.sm...@gmail.com wrote:
 Currently, seeing the same high number of DDEs - requests taking up to
 70seconds. Consequently, instance usage has gone through the roof, and
 we're burning through our daily budget at a rate way higher than normal.
 Not very happy right now!

-- 
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: Very high request latency periods on App Engine

[bFlood]

seeing the same thing on one of my older M/S apps. Nothing has changed
in code but most of the request have huge latency with most in the
pending_ms queue. I started messing with the sliders to see if
anything worked but prior to that (when its been busted for several
days), the sliders were both on full automatic. 4-7 instances running
at any one time and minimal traffic



On Dec 5, 7:43 pm, Brandon Wirtz drak...@digerat.com wrote:
 What is the max idle instances?

 If a request takes 1000ms, and you get 8 at the same time, with 1 Idle
 instance and a 5s spin up you would have time outs with these settings.

 Safe Rule

 If Max pending latency is set to less than the average request time:
 Idle instances must always be = Spin-up time / Average request time

 If pending latency is set to less than average request time, you will ALWAYs
 have to spin up another instance if you get more requests simultaneously
 than you have instances (unless you are on a concurrent platform)







 -Original Message-
 From: google-appengine@googlegroups.com

 [mailto:google-appengine@googlegroups.com] On Behalf Of Alex Epshteyn
 Sent: Monday, December 05, 2011 4:32 PM
 To: Google App Engine
 Subject: [google-appengine] Very high request latency periods on App Engine

 Last week I started noticing periods of very high request latency in my app
 lasting for many hours and even days.  These are not correlated to the
 traffic patterns in my app, and so I assume it's an issue that affects all
 of app engine.  Looking at the logs, it seems that some requests are
 spending way too much time in the pending queue, despite my app's max
 pending latency set to Automatic - 200ms (min - max).

 I filed an issue for 
 this:http://code.google.com/p/googleappengine/issues/detail?id=6447

 This is pretty bad.  Could anyone on the team comment whether this is an App
 Engine problem or something wrong with my app's configuration?

 Thanks,
 Alex

 --
 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 
 athttp://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: application is down on production

[bFlood]

HR is throwing a lot of errors for me right now, slow instance startup
and V3 DB issues (The API call datastore_v3.Get() took too long to
respond and was cancelled.)



On Nov 23, 4:27 am, Brandon Wirtz drak...@digerat.com wrote:
 Which kinds of Instances are you on Master/Slave or High Replication?







 -Original Message-
 From: google-appengine@googlegroups.com

 [mailto:google-appengine@googlegroups.com] On Behalf Of uri twig
 Sent: Wednesday, November 23, 2011 1:19 AM
 To: Google App Engine
 Subject: [google-appengine] Re: application is down on production

 I did'nt understand M/S or HR.

 For reason I can't explain the app is back again, and after a few tried also
 the backends could be started.

 Has someone in google did something?

 Thanks Anyways till next time.

 On Nov 23, 11:03 am, Brandon Wirtz drak...@digerat.com wrote:
  Also, if you are down unexpectedly the last thing you want to do is
  deploy a new version.  When the service is down don't change things
  because if you are changing things when Google is changing things you
  may be really broken after.

  -Original Message-
  From: google-appengine@googlegroups.com

  [mailto:google-appengine@googlegroups.com] On Behalf Of uri twig
  Sent: Wednesday, November 23, 2011 12:22 AM
  To: Google App Engine
  Cc: is...@vod.io
  Subject: [google-appengine] application is down on production

  Hi,
  our app 'vodio-app' is down on production it gives a 500 error, and I
  ca'nt see any new log entries.

  we cant upload any new version, and we can restart backends

  Please advise, it is urgent !!!

  Uri Twig
  CTO Vodio LTD

  --
  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
 athttp://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 
 athttp://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] HR down?

[bFlood]

nothing in the Status page so I'm assuming this is localized to a few
apps but HR instance serving and DB operations are breaking for me
right now

lots of these errors: The API call datastore_v3.Get() took too long
to respond and was cancelled.

started about 9:30 EST

cheers
brian

-- 
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: HR down?

[bFlood]

the instance serving warnings are:

Request was aborted after waiting too long to attempt to service your
request. This may happen sporadically when the App Engine serving
cluster is under unexpectedly high or uneven load. If you see this
message frequently, please contact the App Engine team.

using Python27 with threadsafe turned off


On Nov 23, 10:01 am, bFlood bfl...@spatialdatalogic.com wrote:
 nothing in the Status page so I'm assuming this is localized to a few
 apps but HR instance serving and DB operations are breaking for me
 right now

 lots of these errors: The API call datastore_v3.Get() took too long
 to respond and was cancelled.

 started about 9:30 EST

 cheers
 brian

-- 
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: Cached Requests

[bFlood]

thank you brandon, great info!

On Nov 19, 8:06 pm, Brandon Wirtz drak...@digerat.com wrote:
 Now that it has been up for a few hours.

 Cache hit rate would be a lot higher but this app serves a lot of search
 queries which are Robo-Generated if that traffic were ignored we'd be
 sailing along at about 60% EdgeCache Hits for the first hours of testing.
 This is on our pre-production service so we'll bake for a bit before we
 have numbers across all the entire service in a more natural environment.
 We also have to populate the cache at this point and we don't yet know how
 long that takes which may raise the numbers even more.

 From: google-appengine@googlegroups.com
 [mailto:google-appengine@googlegroups.com] On Behalf Of Jeff Schnitzer
 Sent: Saturday, November 19, 2011 3:57 PM
 To: google-appengine@googlegroups.com
 Subject: Re: [google-appengine] Cached Requests

 Wow, this is exactly the kind of information I have been desperately looking
 for.  If you're ever in the Bay Area I will buy you as many drinks as you
 can stand.  Or sit.  Or pass out into some hottie's lap.

 Jeff

 On Sat, Nov 19, 2011 at 6:42 PM, Brandon Wirtz drak...@digerat.com wrote:

 I have fought back and forth with issues related to the Edge cache.
 Sometimes it would work, sometimes it wouldn't sometimes it would hold on to
 files way too long.

 Well it hadn't been working at all for like 6 weeks, and I didn't mess with
 it, but I got around to it today.

 If you want edge caching to work you need to make sure you have done the
 following things

 1.       Set Public   If you don't set public it won't be cached ever.

 2.       Set a max-age . If you set public but don't specify max-age it
 won't be cached

 3.       Use a comma.  public, max-age=300 works fine.  Public; max-age=300
 does not.

 4.       Set an age greater than 60. 61 seems to cache. 60 does not.  There
 is probably some volume to will I cache based on expiration but 61 seconds
 at the volumes we run seems to cache and 60 doesn't ever seem to.

 5.       Set an age less than 366 days.  364 days seems to work 365 works
 most the time 366 never seems to work.  So those Expire never kinds of
 posts people talk about for versioned assets that never expire.  Well 10
 years is not the right answer.

 6.       Expires with a date, doesn't seem to help, and seemingly may
 prevent caching in some instances.  I think this may be clock drift. Or
 something about how picky the parser is about the format of the date.
 Things that work in browsers don't always work correctly in the edgecache.
 (like the Semi vs the comma)

 7.       Set both Pragma and Cache-Control  If Pragma is not set Public then
 Cache-Control seems to be ignored.

 This is all way more info than you probably need, but. Here is the relevant
 code.

 Here is the python code to set headers for caching  (CACHE_EXPIRE is a
 variable we set based on the page type)

     self.response.headers['Cache-Control'] = 'public, max-age=%d' %
 CACHE_EXPIRE

     self.response.headers['Pragma'] = 'Public'

 This is also available 
 athttp://www.xyhd.tv/2011/11/industry-news/setting-cache-control-header...
 thon-to-take-advantage-of-google-appengines-edgecache/

 --
 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
 mailto:google-appengine%2bunsubscr...@googlegroups.com .
 For more options, visit this group 
 athttp://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 
 athttp://groups.google.com/group/google-appengine?hl=en.

  image001.png
 27KViewDownload

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: URGENT: google checkout for usage i dont know where it comes from.

[bFlood]

good point joshua. a heads up would have been nice but that does make
sense

On Nov 16, 9:31 am, Joshua Smith joshuaesm...@charter.net wrote:
 Well, they have a point about storage. I don't want my data to disappear if I 
 disable my app, and they deserve to get paid for the storage those disabled 
 apps are using.

 On Nov 16, 2011, at 9:27 AM, andreas schmid wrote:







  are you kidding me??
  disabled app and still charged?? this is a joke

  c'mon google guys

  On Nov 15, 2011, at 2:44 PM, Riley wrote:

  This happened to me, too - if you follow the links in the checkout receipt 
  for long enough you eventually get to something with the appid buried in a 
  description.

  In my case, the app was disabled, but I hadn't disabled billing 
  separately, so I was still charged.  Whoops!

  --
  You received this message because you are subscribed to the Google Groups 
  Google App Engine group.
  To view this discussion on the web 
  visithttps://groups.google.com/d/msg/google-appengine/-/fRmkmWeXCPcJ.
  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 
  athttp://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 
  athttp://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: Hosting Mapnik, TileStache in Google App Engine

[bFlood]

hi raj

You won't be able to get Mapnik to run, it definitely has some c
runtime dependencies. As for TileStache, depending on what
functionality you wanted, you might be able to get it running. but
afaik, it uses OGR for data access, so that would be useless on GAE as
well.

all in all, I'm not sure you'll have much luck with either

cheers
brian

On Nov 16, 11:13 am, Raj arthiyagara...@gmail.com wrote:
 Hey,

 Before using google app engine, I thought its not a bad idea to ask to
 wise people in this group.

 My basic requirement is to host,

 Mapnik (Mapnik is a Free Toolkit for developing mapping 
 applications,http://mapnik.org/),
 TileStache (TileStache is a Python-based server application that can
 serve up map tiles based on rendered geographic data,http://tilestache.org/).
 Any direction/insight on this would be helpful.

 As I looked into the 'Google App Engine SDK for Python' : (Windows/Mac
 OS X/Linux/Other Platforms/MapReduce Bundle),
 I am trying to use the 'Linux app engine'(because my production
 environment is linux based). But my development environment is Windows
 based. So, does my download platform(OS) matters? or should I use the
 appropriate one for the respective environment(dev/prod)?

 -Thanks
 Raj

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: URGENT: google checkout for usage i dont know where it comes from.

[bFlood]

greg

are disabled apps being billed the $2.10? I've just received 6 bills
in a row, all for disabled apps

brian

On Nov 15, 5:47 pm, Logan logan.ha...@gmail.com wrote:
 On Nov 14, 3:07 pm, Gregory D'alesandre gr...@google.com wrote:

  Hi Andreas,

  If you have billing enabled App Engine will now charge you $2.10/week as a
  minimum spend.  Above $2.10 we will charge you for what you use.  If you
  don't need to go beyond the free quota, it might make more sense to disable
  billing on your application.  More information can be found 
  here:http://code.google.com/appengine/kb/billing.html#nine_dollar_month_fe...

 I just got billed for two of my idle apps consuming trivial resources.
 I don't recall ever turning on billing for anything, and now I can't
 turn it off despite my card already being charged. I'm not going to
 lose sleep over $4.20, but I'm wondering if I did something in the
 past that subtly turned this on? I also want to be able to change this
 setting NOW.

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine group.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

[google-appengine] Re: URGENT: google checkout for usage i dont know where it comes from.

[bFlood]

yes, i would say so.

On Nov 15, 6:58 pm, Gregory D'alesandre gr...@google.com wrote:
 Yes, you need to disable billing for an app in order to not be charged, no
 disable the app itself.  This should've been better documented.

 Greg







 On Tue, Nov 15, 2011 at 3:55 PM, bFlood bfl...@spatialdatalogic.com wrote:
  greg

  are disabled apps being billed the $2.10? I've just received 6 bills
  in a row, all for disabled apps

  brian

  On Nov 15, 5:47 pm, Logan logan.ha...@gmail.com wrote:
   On Nov 14, 3:07 pm, Gregory D'alesandre gr...@google.com wrote:

Hi Andreas,

If you have billing enabled App Engine will now charge you $2.10/week
  as a
minimum spend.  Above $2.10 we will charge you for what you use.  If
  you
don't need to go beyond the free quota, it might make more sense to
  disable
billing on your application.  More information can be found here:
 http://code.google.com/appengine/kb/billing.html#nine_dollar_month_fe...

   I just got billed for two of my idle apps consuming trivial resources.
   I don't recall ever turning on billing for anything, and now I can't
   turn it off despite my card already being charged. I'm not going to
   lose sleep over $4.20, but I'm wondering if I did something in the
   past that subtly turned this on? I also want to be able to change this
   setting NOW.

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

[google-appengine] Re: Threaded Python AppEngine for Dummies

[bFlood]

You might have seen this already but another user posted this to the
Python group, this is exactly what I am seeing in my testing

http://groups.google.com/group/google-appengine-python/browse_thread/thread/5748848a85cec2e2/35568c4e44135383#35568c4e44135383

http://www.google.com/url?sa=Dq=https://docs.google.com/document/d/1cbiFN7ONeubDW-qDaRFuK4mtyO3kEfA9qhGEDUVdJ4w/edit%3Fpli%3D1usg=AFQjCNEoVyzVirccwqGOcNu0blXt1jUB1Q


cheers
brian


On Nov 5, 10:01 am, bFlood bfl...@spatialdatalogic.com wrote:
 thanks Anand, good to know you guys are on the case. Brandon's comment
 gave me hope so I looked into my code a little deeper. Here are a
 couple of comments (I'm by no means a Python expert so I'm unsure
 about a GIL details)

 1) I still see the issue above, random delays between calls under
 load. For example, a call to memcache takes a few ms on one request
 but then takes 200-300ms on another. Under no load it always quick

 2) access from the native appspot.com domain seems faster then a
 custom one (I can't remember if this is an issue with the existing
 runtime too)

 3) on one of my larger tests involving existing code that was running
 horribly in the threaded runtime , the main culprit turned out to be
 the xml minidom. I'm assuming it's not threadsafe so I'll need to move
 to lxml

 4) I use a lot of static class methods, I'm not sure if the class def
 is locked by the GIL (I had thought not)

 Is this threadsafe with the GIL?
 class Util():
     @staticmethod
     def DoSomething():
          pass

 5) I'm using webapp2, are there any know issues there?

 6) Are async RPC calls necessary to get the threadsafe benefits (ex
 async urlfetch)? or can we use the standard sync calls as well?

 thanks, python27 is going to be great
 brian

 On Nov 4, 9:42 pm, Anand Mistry amis...@google.com wrote:







  Although I can't get into any details, we are aware of these issues in the
  python27 runtime. Like you noted, the runtime is experimental (hey, we've
  only been live for one release cycle), and improvements are still coming.

  On a more general note, the python27 runtime is implemented using the
  CPython interpreter from python.org and hence is open to issues related to
  the GIL. I suggest 
  readinghttp://wiki.python.org/moin/GlobalInterpreterLocktoget some 
  background
  into multi-threading performance issues in Python.

-- 
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: Threaded Python AppEngine for Dummies

[bFlood]

thanks Anand, good to know you guys are on the case. Brandon's comment
gave me hope so I looked into my code a little deeper. Here are a
couple of comments (I'm by no means a Python expert so I'm unsure
about a GIL details)

1) I still see the issue above, random delays between calls under
load. For example, a call to memcache takes a few ms on one request
but then takes 200-300ms on another. Under no load it always quick

2) access from the native appspot.com domain seems faster then a
custom one (I can't remember if this is an issue with the existing
runtime too)

3) on one of my larger tests involving existing code that was running
horribly in the threaded runtime , the main culprit turned out to be
the xml minidom. I'm assuming it's not threadsafe so I'll need to move
to lxml

4) I use a lot of static class methods, I'm not sure if the class def
is locked by the GIL (I had thought not)

Is this threadsafe with the GIL?
class Util():
@staticmethod
def DoSomething():
 pass

5) I'm using webapp2, are there any know issues there?

6) Are async RPC calls necessary to get the threadsafe benefits (ex
async urlfetch)? or can we use the standard sync calls as well?

thanks, python27 is going to be great
brian








On Nov 4, 9:42 pm, Anand Mistry amis...@google.com wrote:
 Although I can't get into any details, we are aware of these issues in the
 python27 runtime. Like you noted, the runtime is experimental (hey, we've
 only been live for one release cycle), and improvements are still coming.

 On a more general note, the python27 runtime is implemented using the
 CPython interpreter from python.org and hence is open to issues related to
 the GIL. I suggest readinghttp://wiki.python.org/moin/GlobalInterpreterLockto 
 get some background
 into multi-threading performance issues in Python.

-- 
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: Threaded Python AppEngine for Dummies

[bFlood]

does anyone else find the python27/threadsafe option slow? in some
simple testing, I'm getting a lot of pending_ms and throttle_code=1
flags in the logs. These are dead simple requests that response in
20-30ms under no load. With a couple concurrent requests, the
execution time can jump to over 1000ms (ignoring the standard cold
starts). I've let the app warm up a little and start a few instances
but the delays are still there (I've also tried full automatic on the
sliders as well as 10 idle instances with 10ms delay)

what's strange is the delays are either pending_ms related or spread
throughout the request (as if the multiple requests per instance are
affecting each other, which I realize should occur but not to this
level. if this is it, it's worthless). These are pretty simple
requests (one memcache request, output to json) so there's no global
locking that could be slowing it down

or, this is just experimental and all of the optimizations are not
even in place yet. hoping for this :)


On Nov 3, 12:49 pm, Sami Lehtinen samlehpro...@yahoo.co.uk wrote:
 Hi,

 I have been browsing around and I still don't know how many parallel
 tasks one instance can handle if multithreading is enabled. I haven't
 seen exact figure or any logical description how this value is being
 calculated for each application.

 Could someone tell me?

  - Thank you!

 --
 Sami Lehtinenhttp://www.sami-lehtinen.net/

-- 
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: Prerelease SDK 1.5.5 available for download!

[bFlood]

any chance the Python27 Trusted Tester user group could be opened so
we can see the discussions from the previous months?

great release, congrats guys



On Oct 4, 2:26 pm, Jeff Schnitzer j...@infohazard.org wrote:
 For XG, look at DatastoreService.beginTransaction(TransactionOptions)

 Jeff







 On Tue, Oct 4, 2011 at 11:15 AM, Barry Hunter barrybhun...@gmail.com wrote:
  Unfortunately its sort of catch-22. Without docs, its makes it very
  hard to figure out how to use the new feature - to be able to test it :(

  Granted some of the changes don't need documentation, eg the limits
  being raised. Perusing the source, is often enlightening, but
  cumbersome.

  On Tue, Oct 4, 2011 at 6:51 PM, Ikai Lan (Google) ika...@google.com wrote:
  No external docs for anything yet (see my original post). We're working to
  get this out as quickly as possible. Where we can really be helped is if
  everyone here looking forward to the release did some local testing of the
  SDK. We'll likely uncover bugs in our testing, but the sooner we can 
  uncover
  things, the sooner we can get this out.
  --
  Ikai Lan
  Developer Programs Engineer, Google App Engine
  plus.ikailan.com | twitter.com/ikai

  On Tue, Oct 4, 2011 at 8:34 AM, Tapir tapir@gmail.com wrote:

  The: Cross Group (XG) transactions.feature should be added earlier.
  It is so important, especially for nosql app.

  On Oct 4, 3:40 am, Ikai Lan (Google) ikai.l+gro...@google.com
  wrote:
   Hey everyone,

   Prerelease SDK 1.5.5 is now available for download! You can get it here:

   Python:http://code.google.com/p/googleappengine/downloads/detail?name=google...

   Java:http://code.google.com/p/googleappengine/downloads/detail?name=appeng...

   We provide prerelease SDKs as previews for things to come. New features
   should not work in production yet, and documentation is typically still
   a
   work in progress. Release notes are below as well as in the prerelease
   packages:

   Python
   ===
   - Python 2.7 is now available as an experimental runtime for all
   applications
     using the High Replication Datastore. To upload your app to the Python
   2.7
     runtime, change the runtime argument in your app.yaml to python27.
   - We have released an experimental utility, available in the Admin
   Console,
   to
     assist in migrating your application to the High Replication
   datastore.
   This
     utility allows you to copy the bulk of your data in the background,
   while
   the
     source application is still serving. You then need a brief read-only
   period to
     migrate your application data while you copy the data that has changed
   from
     the time the original copy started.
   - We have increased the number of files you can upload with your
   application
     from 3,000 to 10,000.
   - We have increased the size limit for a single file uploaded to App
   Engine
   from
     10MB to 32MB.
   - We have increased the Frontend request deadline from 30 seconds to 60
   seconds.
   - We have increased the URLFetch maximum deadline from 10 seconds to 60
   seconds.
   - We have increased the URLFetch Post payload from 1MB to 5MB.
   - App Engine now supports Cross Group (XG) transactions with the High
     Replication Datastore, which allow you to perform transactions across
     multiple entity groups.
   - We have released an experimental API that can write to Google Storage
   for
     Developers directly from App Engine.
   - We have added a graph to the admin console that displays the number of
     instances for which you will be billed.
   - In the XMPP API, get_presence() is deprecated in favor of using the
   inbound
     presence handlers documented in

  http://code.google.com/appengine/docs/python/xmpp/overview.html#Handl...
   .
   - The Task Queue API 'target' parameter now accepts a new value,
     taskqueue.DEFAULT_APP_VERSION, which will send the task to the default
     frontend version, rather than the version or backend where the 'add'
   method is
     being called.
   - In the URLFetch API, make_fetch_call() now returns an RPC object.
   - Fixed an issue in the Admin Console where the Run Now button did not
   work
     for tasks with a '-' in the name.
   - Fixed an issue where the SDK did not decode Base64 encoded blobs.
   - Fixed an issue to provide a better error message when using the Mail
   API
   to
     send email to an invalid user address.
   - Fixed an issue in the SDK where a skip_files entry caused an
   ImportError
   when
     the library was located elsewhere in the PYTHONPATH.
   - Fixed an issue in the SDK index viewer where the arrows indicating
   whether
   a
     query was ascending or descending were not properly rendered.
   - Fixed an issue where httplib did not support the deadline argument for
     URLFetch calls.
      http://code.google.com/p/googleappengine/issues/detail?id=2216
   - Fixed an issue where you could not schedule a cron job to run 

[google-appengine] Re: delaying pricing change

[bFlood]

+100

On Sep 1, 12:23 pm, Mark Bucciarelli mkb...@gmail.com wrote:
 i assume you guys must be getting some serious
 pressure from upper management to start making
 some money here.

 but asking us to:

   (1) convert to HR to get the SLA and

   (2) convert to multithreading

 is asking a lot.  asking it in a short time frame is
 not realistic, especially for someone running a
 large app in production with many users.

 threads suck.  they introduce a ton of
 complexity---race conditions that are hard
 to imagine, and mostly impossible to reproduce
 in a reliable way during unit testing.

 is there any possibility you can delay the price
 increase until after 2.7 is out and you have
 published some good docs on how to safely
 move to multi-threading and HR?

 thanks,

 m

-- 
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: Suddenly started to get Unauthorized sender when sending emails

[bFlood]

yea, is there an ETA? should we all just switch to different accounts
for email?

On Aug 15, 7:59 am, Joshua Smith joshuaesm...@charter.net wrote:
 I'm still seeing this error.  Google team: Can you give us an ETA for this 
 fix?

 If you think it's going to take days to fix, I'll set up a non-dot email to 
 send the emails, but if you think it'll be fixed soon, I won't bother (I 
 always send email in a task queue task because email throws so many bizarre 
 exceptions, so they're just sitting there retrying…)

 (I'm hesitant to implement the non-dot work-around, since my users might not 
 get those emails because they've never seen a message from that address 
 before, and therefore it may be considered spam.  I'd rather that they get 
 them late than not at all.)

 -Joshua

-- 
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: Suddenly started to get Unauthorized sender when sending emails

[bFlood]

+1 sender has a period in it

On Aug 13, 3:09 am, Jan Muller mulle...@gmail.com wrote:
 My sender address also contains .

 Jan Müller

 On Sat, Aug 13, 2011 at 2:12 AM, Joshua Smith joshuaesm...@charter.netwrote:







  +1.  My problem sender does, indeed, have a . in the account name.

  On Aug 12, 2011, at 7:17 PM, Takashi Matsuo (Google) wrote:

  Hi everyone.

  We're aware of this issue and working for the fix.

  The issue we're seeing is that if the sender's(who is also an app's owner)
  mail address contains . (dot), the mail sending call raises an error.

  Sorry for the inconvenience.
  If you observe different issue, please let us know.

  -- Takashi

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

[google-appengine] Re: Suddenly started to get Unauthorized sender when sending emails

[bFlood]

I'm getting these too and the sender is definitely an admin on the
account (in fact it's the one used to deploy, so I know it's valid and
working)

help Google, no emails are going out


On Aug 12, 1:08 am, anatoliy anatoliy.arteme...@gmail.com wrote:
 Hi!

 Tonight appengine started to throw:

 javax.mail.SendFailedException: Send failure
 (javax.mail.MessagingException: Illegal Arguments
 (java.lang.IllegalArgumentException: Unauthorized Sender: Unauthorized
 sender))

 for the same code as was working perfectly yesterday.

 Sender is set using this code:
 mimeMsg.setFrom(new InternetAddress(my app ad...@gmail.com, my app
 admin));

 Anyone else having same problem?

 anatoliy

-- 
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: Duplex Web Service possible ?

[bFlood]

plus they got this great video :)

http://bitly.com/lkF5Ff

On Jun 15, 7:38 pm, Calvin calvin.r...@gmail.com wrote:
 I'll second this.  My experiments with PubNub were very promising.

-- 
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: Duplex Web Service possible ?

[bFlood]

how about http://www.pubnub.com



On Jun 14, 10:53 am, Barry Hunter barrybhun...@gmail.com wrote:
 Not really. AppEngine basically uses a 'request/responce' method.
 basically CGIhttp://www.w3.org/CGI/

 AppEngine can't keep connections open. Its designed for HTTP requests

 There is the ChannelAPI, which makes persistant connections possible
 (using long-polling?) but doesnt sound suitable (its still HTTP).

 xmpp directly might be useful as a communication medium. I dont really
 know much about it. Perhaps you can use it without involving
 AppEngine. Or AppEngine could be a 'controller' or a 'mediator' so
 that devices can find each other.

 On Tue, Jun 14, 2011 at 2:33 PM, Richard Roylance







 roylance.rich...@gmail.com wrote:
  Hi,

  Is it possible to host a duplex web service on GAE ?

  Basically I am wanting to have a mobile app and a desktop app that will
  message each other through a duplex web service. I currently have this
  working using a TCP socket connection, but obviously this will not work
  unless the 2 devices are on the same network. That is why i need to make a
  duplex web servioce to facilitate the communication.

  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/-/wJmJCwYvVVAJ.
  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: Go Language

[bFlood]

is this available on GAE now? also, can multiple goroutines be used to
service user requests from a single instance? I had though the Go blog
had stated this wasn't available on GAE yet



On Jun 12, 8:52 pm, Ikai Lan (Google) ika...@google.com wrote:
 Depends on how much number crunching. I say just use the language you like
 the best. Unless you're doing some kind of non-linear ops (and a LOT of
 them) you might not get the efficiency you're looking for moving to Java.
 The number crunching would have to be very significant relative to the time
 it takes to do IO for language speed to make a difference for simple math.

 One advantage the Go runtime has over Python and Java is that you can fire
 off Goroutines within a process. A Goroutine is to Go what a Thread is to
 Java or a fork is to Python. You communicate between Goroutines using
 channels and multiplex channels using the select statement. If you can
 break up your heavy computation into lots of small bits, you will consume
 the same amount of CPU but will consume less wallclock time, returning to
 the user faster.

 Ikai Lan
 Developer Programs Engineer, Google App Engine
 Blog:http://googleappengine.blogspot.com
 Twitter:http://twitter.com/app_engine
 Reddit:http://www.reddit.com/r/appengine







 On Mon, Jun 13, 2011 at 7:47 AM, supercobra superco...@gmail.com wrote:
  Go is slower than Java and Java has all the libraries and tools (IDE,
  debuggers, refactoring, profiling, etc...) that you'll need.

  Here are the speed test results from a Google study:

 http://www.readwriteweb.com/hack/2011/06/cpp-go-java-scala-performanc...

  -- superco...@gmail.com
 http://supercobrablogger.blogspot.com/

  On Sun, Jun 12, 2011 at 6:39 PM, jay kyburz@gmail.com wrote:
   Hi All,

   Anybody had a chance to play around with Go yet?

   My games are CPU heavy because I do a lot of number crunching on game
   data every time a user requests the game page. This code really has
   nothing to do with app engine but is pure game code. I would image
   this code would be significantly faster that Python.

   Anybody have any experiences to share yet?

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

-- 
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: HItting query limit using Geocoding API from App Engine

[bFlood]

Google Maps Premium
http://www.google.com/enterprise/earthmaps/maps.html

Dev guide for Url signing
http://code.google.com/apis/maps/documentation/premier/guide.html



On Apr 8, 3:31 am, Ikai Lan (Google) ika...@google.com wrote:
 I'll admit that I don't understand the maps API to be an authority on this,
 but the last time I spoke to them, they mentioned some kind of a key you can
 get a hold of? With this key you can make signed requests that can be
 whitelisted. Otherwise, you're put into the general pool of IPs and subject
 to throttling.

 Ikai Lan
 Developer Programs Engineer, Google App Engine
 Blog:http://googleappengine.blogspot.com
 Twitter:http://twitter.com/app_engine
 Reddit:http://www.reddit.com/r/appengine







 On Fri, Apr 8, 2011 at 12:20 AM, nickmilon nickmi...@gmail.com wrote:
  IMHO a proxy will complicate things.
  What about if GAE team gets in touch with maps V3 team and explain to
  them the issue so may be they can rate limit all GAE originated appls
  by app id which is a very secure method since app id can't be
  hacked ?

  @Joe sorry my api isn't that useful in your case.
  Regards
  Nick

  On Apr 7, 1:06 am, Brandon Wirtz drak...@digerat.com wrote:
   Use a Proxy.  Then you can come through your own IP-pool.

   From: google-appengine@googlegroups.com
   [mailto:google-appengine@googlegroups.com] On Behalf Of Joe Tyson
   Sent: Wednesday, April 06, 2011 2:59 PM
   To: google-appengine@googlegroups.com
   Subject: Re: [google-appengine] Re: HItting query limit using Geocoding
  API
   from App Engine

   We are delegating some of that to the client now, but it is far

   less than ideal. Our client is mobile, so every byte that we send

   over can end up costing our users money (you would be surprised

   how sensitive some people are to this).

   Thanks for the resource, though. I wish country level would be

   enough information for us :-(.

   Doing some additional searching around, it looks this issue has

   been bought up by some other users on the maps forum:

  http://goo.gl/RyJ9w

   On Wednesday, April 6, 2011 at 2:44 PM, nickmilon wrote:

   May be you can delegate the geocoding job to the client side using
   js ?
   also you can take a look here :
 http://gaengine.blogspot.com/2010/11/world-countries-and-ip-geocoding...
   ml

   Nick ;-)

   On Apr 6, 7:25 pm, Joe Tyson joety...@gmail.com wrote:

   Hello,

   This seems to be more of a problem with the geocoding api than app
  engine,
   but I'm unable to get ahold of anyone on that team so I'll post here
   instead.

   The new Geocoding API doesn't do any form of url signing or api keys for
   non-premier accounts and resorts to using IP address to control quotas.
   Since App Engine uses a shared IP pool, my app gets clumped in the quota
   limitations of other apps. This must be a somewhat frequent problem for
   other apps, since 90% of my geocoding attempts get an 'OVER_QUERY_LIMIT'
   message. These last few days, it has been closer to 100% at 500-600
  queries
   spread out over an 15-20 hours.

   I'll add that I don't think using a pool of IPs is at all the issue. Any
   large scale deployment would be hitting the Geocoding API from a pool of
   IPs, and if the pool were dedicated to a single service, the service
  would
   be circumventing the Geocoding API quotas anyway.

   Is anyone else on the list having this issue? Have you been able to work
   with the geocoding team to get auth tokens that don't require having a
   premier account?

   joe

   --
   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 athttp://
  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 athttp://
  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 

[google-appengine] Re: Pre-Call Hooks to UrlFetch Not Working - possible bug?

[bFlood]

thank you for this patch!

On Mar 3, 10:04 pm, David Lehn dil...@gmail.com wrote:
 On Thursday, March 3, 2011 9:37:21 PM UTC, Aaron wrote:

  In my testing, it seems like setting a default deadline for urlfetch
  is not working in production.  I have replicated the behavior that I'm
  seeing in the barest form below.  Essentially, I'm trying to do a GET
  request for a URL that hangs for six seconds before returning.  With
  the default time out of 5 on urlfetch, this times out.  So, I'm trying
  to use a pre-call hook to extend the default timeout to 10 seconds.
  ...

 We were talking on IRC and solved this with a monkey patch method to setup a
 custom default deadline. Just add the following before you directly or
 indirectly import urlfetch. In Aaron's case, urlfetch is being used via
 httplib.

 from google.appengine.api import urlfetch
 real_fetch = urlfetch.fetch
 def fetch_with_deadline(url, *args, **argv):
     argv.setdefault('deadline', 10)
     return real_fetch(url, *args, **argv)
 urlfetch.fetch = fetch_with_deadline

 --dave

-- 
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: High Replication or Master/Slave?

[bFlood]

i think he meant that *interaction* with HR is more consistent (e.g.
most requests are in a fixed performance range, whereas there are more
perf spikes with MS).

nice charts guys, those are helpful!

On Mar 1, 9:50 am, Geoffrey Spear geoffsp...@gmail.com wrote:
 On Mar 1, 8:18 am, Simon Knott knott.si...@gmail.com wrote:

  What makes you think HR is slower than M/S?  This is the case for
  Puts/Deletes, but for Gets and Querying it's faster and much more
  consistent.

 Where do you get much more consistent from?  The HR datastore is
 eventually consistent; the M/S datastore is strongly consistent.

-- 
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: Deployment Failing with 500 error.

[bFlood]

I just saw the same thing, 503 error on upload. Disabled
precompilation and the upload continued successfully

On Feb 25, 2:59 am, Eric Ka Ka Ng ngk...@gmail.com wrote:
 Hi Ikai,

 We experienced 503 error during the pre-compilation stage during deployments
 to all our apps in this hour. would try to disable precompilation first and
 re-enable it later when this problem has been fixed

 - eric

 On 10 December 2010 06:50, Ikai Lan (Google) ikai.l+gro...@google.comwrote:







  When there's a deploy failure, it helps us if you let us know the exact
  error. With a 503, one thing to try is to disable precompilation and let us
  know. We're monitoring these services, but you can help us more quickly
  diagnose the problem with this information.

  --
  Ikai Lan
  Developer Programs Engineer, Google App Engine
  Blogger:http://googleappengine.blogspot.com
  Reddit:http://www.reddit.com/r/appengine
  Twitter:http://twitter.com/app_engine

  On Wed, Dec 8, 2010 at 2:27 PM, dloomer dloo...@gmail.com wrote:

  I see the title of the thread was changed to reflect 500 instead of
  503, but the log dump I get, and which I assume the OP gets, is:

  Error 503: --- begin server output ---
  Try Again (503)
  An unexpected failure has occurred. Please try again.
  --- end server output ---
  2010-12-08 16:25:24 (Process exited with code 1)

  On Dec 8, 3:32 pm, Nick Renny nickre...@gmail.com wrote:
   Not getting anything through with deploy. failing at pre-compilation
   with 500 errors - for the last 2 hours

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

-- 
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: Interested in giving us your thoughts on App Engine?

[bFlood]

this looks to me like the features associated with GAEfB are now being
offered as add-on services to traditional GAE users. If all other
billing in GAE stays the same and we can now add these premium
services piecemeal for a monthly price, that sounds like a big win to
me. The per-user pricing that GAEfB originally had was problematic for
sites that needed to serve both internal and external customers

my two cents...
b



On Feb 11, 9:19 am, Geoffrey Spear geoffsp...@gmail.com wrote:
 On Friday, February 11, 2011 2:00:09 AM UTC-5, gops wrote:

  3) For, HTTPS, Google is already charging extra for secure requests.
  Why separate billing ?

 For this one, I suspect it would involve giving applications static IP
 addresses, since TLS/SNI still isn't supported on most browsers on Windows
 XP, and the installed base of XP machines doesn't seem to be going away any
 time soon.

-- 
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: Deployment failing

[bFlood]

+1

On Jan 12, 11:50 am, Felippe Bueno felippe.bu...@gmail.com wrote:
 +1







 On Wed, Jan 12, 2011 at 2:49 PM, Ryan Goldstein r...@moberg.com wrote:
  Spoke too soon; deployment is failing again.

  -Ryan

  On Jan 12, 11:16 am, Ryan Goldstein r...@moberg.com wrote:
  ... and now it's working again. Problem solved!

  -Ryan

  On Jan 12, 11:14 am, Ryan Goldstein r...@moberg.com wrote:

   Update: On my subsequent attempt, the console showed the following
   after Initiating update.

   --
   javax.net.ssl.SSLHandshakeException: Remote host closed connection
   during handshake
   --

   -Ryan

   On Jan 12, 11:06 am, Ryan Goldstein r...@moberg.com wrote:

I've been updating and redeploying my app today (appid:
mobergdrmserver). It took progressively longer to deploy, and my most
recent attempt failed.

From my Eclipse console during my most recent deployment attempt:

...
Creating staging directory
Scanning for jsp files.
Scanning files on local disk.
Initiating update.
Cloning 29 static files.
Cloning 66 application files.
Uploading 1 files.
Uploaded 1 files.
Initializing precompilation...
Deploying new version.
Will check again in 1 seconds.
Will check again in 2 seconds.
Will check again in 4 seconds.
Will check again in 8 seconds.
Will check again in 16 seconds.
Will check again in 32 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
Rolling back the update.
java.lang.RuntimeException: Version not ready.

The debug logs are as follows:
Unable to update:
java.lang.RuntimeException: Version not ready.
        at
com.google.appengine.tools.admin.AppVersionUpload.commit(AppVersionUpload.j
 ava:
516)
        at
com.google.appengine.tools.admin.AppVersionUpload.doUpload(AppVersionUpload
 .java:
129)
        at
com.google.appengine.tools.admin.AppAdminImpl.update(AppAdminImpl.java:
56)
        at
com.google.appengine.eclipse.core.proxy.AppEngineBridgeImpl.deploy(AppEngin
 eBridgeImpl.java:
271)
        at
com.google.appengine.eclipse.core.deploy.DeployProjectJob.runInWorkspace(De
 ployProjectJob.java:
146)
        at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorksp
 aceJob.java:
38)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Thanks,
-Ryan

  --
  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-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to 
  google-appengine+unsubscr...@googlegroups.com.
  For more options, visit this group 
  athttp://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-appeng...@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] Availability of GAE app for Google Apps users

[bFlood]

I don't know what our admin did for our Google Apps domain but we can
now successfully log into GAE apps. I'm assuming it's whatever
procedure Josh was talking about. it seems to works well, I can now log
in using either a GMail or Google Apps email account


cheers
brian

-- 
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-appeng...@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: Scaleability and the magic 1000ms request time

[bFlood]

which in turn affects the capacity available for running offline
tasks - so, if you have a low volume site, you won't get that many
instances for your tasks? likewise, if you have some user facing
requests that go longer then 1000ms (by design or otherwise), the
instances available for your tasks are impacted? or am I confused?

On Sep 16, 8:44 am, Nick Johnson (Google) nick.john...@google.com
wrote:
 Hi Jason,

 The same appservers are used to serve user-facing and offline traffic. The
 volume of user-facing traffic (that is below the latency threshold) you
 serve determines how many appservers we provision for your application,
 which in turn affects the capacity available for running offline (task queue
 and cron) tasks.

 -Nick Johnson





 On Thu, Sep 16, 2010 at 1:41 PM, Jason C jason.a.coll...@gmail.com wrote:
  The number of instances that App Engine makes available to your
  application depends on if you keep your average request time under
  1000ms for user-facing requests.

  Ikai Lan (I believe) said that taskqueue and cron job requests do not
  count against this boundary. Ikai also said that this boundary was in
  place because longer requests were bad for the ecosystem.

  Since taskqueue and cron job requests do not count against this
  boundary, in order for them to not be bad for the ecosystem, I'm
  guessing that they are served from a different set of servers than
  user-facing requests are.

  We (appid: steprep) have a number of external machines that also hit
  our urls. While we make every effort to keep user-facing requests
  quick and responsive, we often use many seconds serving the requests
  that are built for external machines (by design).

  It has only just struck me this morning that this could be having a
  bad (perhaps dramatic) impact on our overall scaleability.

  First off, is it true that cron and taskqueue items are served on a
  different set of servers? If so, is there any way to designate that a
  particular url is being requested by a machine and can be routed to
  this alternate set (of presumably slower) servers (e.g., a request
  header)?

  If I'm way off on all of this, and if taskqueue and cron jobs are
  served from the same set of servers, I'm not sure how the bad for the
  ecosystem argument holds, and perhaps Google should revisit this
  1000ms boundary condition altogether.

  --
  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-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2Bunsubscrib 
  e...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.

 --
 Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. ::
 Registered in Dublin, Ireland, Registration Number: 368047
 Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
 368047

-- 
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-appeng...@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: Scaleability and the magic 1000ms request time

[bFlood]

Ikai - can we assume by your answer that the task queue is in fact
impacted by user facing requests? the task queue is setup to handle 40
requests/second, how could you ever get this performance if the
instance count is dictated by user requests?

if this is the case, then the only way to get decent task queue
performance on a low volume site is to bombard it with small, no-op
requests so your app instance count increases.

is this just patchwork fixes until the long running processes (from
the Roadmap) is complete?

On Sep 16, 10:05 am, Ikai Lan (Google) ikai.l+gro...@google.com
wrote:
 Jason, I think your situation is fine. Offline tasks have the property that,
 unlike user-facing tasks, do not require instant execution. If you schedule
 an offline task for now, that actually means when there's capacity and
 App Engine can allocate idle capacity to process your request. Thus, the
 need to spin up additional instances is unnecessary in most cases. Are you
 seeing that your tasks are backed up?



 On Thu, Sep 16, 2010 at 12:56 PM, bFlood bflood...@gmail.com wrote:
  which in turn affects the capacity available for running offline
  tasks - so, if you have a low volume site, you won't get that many
  instances for your tasks? likewise, if you have some user facing
  requests that go longer then 1000ms (by design or otherwise), the
  instances available for your tasks are impacted? or am I confused?

  On Sep 16, 8:44 am, Nick Johnson (Google) nick.john...@google.com
  wrote:
   Hi Jason,

   The same appservers are used to serve user-facing and offline traffic.
  The
   volume of user-facing traffic (that is below the latency threshold) you
   serve determines how many appservers we provision for your application,
   which in turn affects the capacity available for running offline (task
  queue
   and cron) tasks.

   -Nick Johnson

   On Thu, Sep 16, 2010 at 1:41 PM, Jason C jason.a.coll...@gmail.com
  wrote:
The number of instances that App Engine makes available to your
application depends on if you keep your average request time under
1000ms for user-facing requests.

Ikai Lan (I believe) said that taskqueue and cron job requests do not
count against this boundary. Ikai also said that this boundary was in
place because longer requests were bad for the ecosystem.

Since taskqueue and cron job requests do not count against this
boundary, in order for them to not be bad for the ecosystem, I'm
guessing that they are served from a different set of servers than
user-facing requests are.

We (appid: steprep) have a number of external machines that also hit
our urls. While we make every effort to keep user-facing requests
quick and responsive, we often use many seconds serving the requests
that are built for external machines (by design).

It has only just struck me this morning that this could be having a
bad (perhaps dramatic) impact on our overall scaleability.

First off, is it true that cron and taskqueue items are served on a
different set of servers? If so, is there any way to designate that a
particular url is being requested by a machine and can be routed to
this alternate set (of presumably slower) servers (e.g., a request
header)?

If I'm way off on all of this, and if taskqueue and cron jobs are
served from the same set of servers, I'm not sure how the bad for the
ecosystem argument holds, and perhaps Google should revisit this
1000ms boundary condition altogether.

--
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.comgoogle-appengine%2Bunsubscrib
 e...@googlegroups.comgoogle-appengine%2Bunsubscrib
  e...@googlegroups.com
.
For more options, visit this group at
   http://groups.google.com/group/google-appengine?hl=en.

   --
   Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd.
  ::
   Registered in Dublin, Ireland, Registration Number: 368047
   Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration
  Number:
   368047

  --
  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-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2Bunsubscrib 
  e...@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-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com

[google-appengine] Re: Please Stop Throttling my App!

[bFlood]

not for nothing, but isn't we may not schedule additional servers for
your app throttling?

when did 700ms become a magic number?



On Sep 15, 9:33 am, Nick Johnson (Google) nick.john...@google.com
wrote:
 Hi,

 We don't throttle apps. If your average latency is over 700 milliseconds for
 user-facing requests, we may not schedule additional servers for your app,
 however.

 What leads you to conclude that your app is being throttled?

 -Nick Johnson

 On Tue, Sep 14, 2010 at 9:47 PM, Coding Social codingsoc...@gmail.comwrote:





  Hi,

  I have had appid mapthislink for many months now.  Recently my
  extensions that use this web service to unwind urls have been featured
  by Google Chrome and Apple Safari so usage is up substantially.

  Can someone turn off the throttle?  Causing latency and 13% error
  rate.

  Thank you.

  --
  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-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2Bunsubscrib 
  e...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.

 --
 Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. ::
 Registered in Dublin, Ireland, Registration Number: 368047
 Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
 368047

-- 
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-appeng...@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: 500 error trying to reach dashboard

[bFlood]

same here and most (not all) GAE requests over multiple apps seem
really slow

On Sep 15, 11:25 am, Francois Masurel fm2...@mably.com wrote:
 Yep, same problem here.

 On Sep 15, 12:50 pm, Fredrik Bonander



 carl.fredrik.bonan...@gmail.com wrote:
  I've had problems with reaching the dashboard since yesterday with 2 
  different applications.

  Is this related to the problems with the datastore?

  ..fredrik

  --
  Fredrik Bonander
  carl.fredrik.bonan...@gmail.com
  +46 70 943 5441

  - the infinite power of the creative mind -

-- 
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-appeng...@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: Please Stop Throttling my App!

[bFlood]

does this count for the Task Queue as well? if so, how are we suppose
to run tasks that span a couple of seconds? are you saying that if one
task goes over 1000ms, you're not going to get any new instances? does
this ban on new instances last for a certain time period?

urlfetch - does one bad network hop (over 1000ms, for whatever reason)
cause you not to scale as well (i'm guessing yes)?

On Sep 15, 5:38 pm, Ikai Lan (Google) ikai.l+gro...@google.com
wrote:
 If it scaled linearly like that, we probably wouldn't have problems with
 long running requests. Unfortunately, long running requests are bad for the
 ecosystem because they impose a non-linear cost.

 The number is officially 1000ms. We have been saying 800ms because we allow
 for some variance. If you tuned your requests to be 990ms and had a period
 of 10ms of latency, you'd be dead in the water. 800ms is a safe enough
 number that even if you experienced an additional spike of 100ms-150ms for
 whatever reason (datastore slowness, unusual usage patterns in your
 application causing Memcache misses, network latency via URLFetch), you can
 tolerate it and be fairly confident you will be autoscaled.



 On Wed, Sep 15, 2010 at 6:51 PM, Flips philip.mates...@driggle.com wrote:
  @Harshal
  Actually slower requests mostly consume more cpu time and are much
  more expensive by default..

  On Sep 15, 8:28 pm, Harshal p.hars...@gmail.com wrote:
   I am OK with Google introducing tiered pricing for handle this issue.
  Don't
   take these numbers at their face values, but you would get the point I am
   trying to make here.

   Avg. Requests               CPU Charges

700ms                         $0.02/hr
1500ms                        $0.04/hr
2000ms                        $0.06/hr

   For all the requests Google provision new servers but if you requests
  take
   longer you pay higher. Not sure if it really makes sense, but the idea of
   totally not allowing any scaling up is not good enough motivation to
  write
   ever more complex apps.

   On Wed, Sep 15, 2010 at 10:51 PM, Jeff Schwartz jefftschwa...@gmail.com
  wrote:

+1 and a whole lot more :(

While it is all our goals to produce efficient applications that can be
scaled out, the platform itself has to be usable , might I add,
  enforce
ceilings that don't choke the life out of even the simplest of
  processes. In
that regard I'd be willing to give up a little bit of scalability for
somewhat more relaxed quotas.

But the real issue I believe is that of imposing unrealistic quotas. It
  is
one thing to show an example of an efficient application built by
  Google and
another to show how that relates to real world applications that though
  they
employ all the same best practices still cannot function within the
allowable quotas.

Resiliency is also a major issue on App Engine, if 99% of our code is
protect the app from what can go wrong and that eats up our quota, what
  is
left for doing real work?

It is my desire and I suppose that of many if not even most of the
  other
developers that Google rethink their approach to providing scalability
  
resiliency to the masses on App Engine.

Jeff

On Wed, Sep 15, 2010 at 12:41 PM, Gordon hall...@gmail.com wrote:

bothering, indeed..

On Sep 15, 6:11 pm, Robert Kluin robert.kl...@gmail.com wrote:
 I am starting to get concerned.  A few months ago this number was
 1000ms, right?  Then about a month or two ago it became 850ms;
 actually I have even saw the 850 number posted within the last week.
 Now it is 700ms?

 From my experience, getting or putting even a single entity can use
  a
 substantial portion of 700ms (20% to 40%).  If you operate on
  multiple
 entities you'll easily use 1/2 of 700ms.  Just the act of _running_
  a
 query takes around 250ms -- when the datastore is actually
  functioning
 correctly.

 This trend is _really_ not good.

 Robert

 On Wed, Sep 15, 2010 at 10:18, bFlood bflood...@gmail.com wrote:
  not for nothing, but isn't we may not schedule additional servers
  for
  your app throttling?

  when did 700ms become a magic number?

  On Sep 15, 9:33 am, Nick Johnson (Google) 
  nick.john...@google.com
  wrote:
  Hi,

  We don't throttle apps. If your average latency is over 700
milliseconds for
  user-facing requests, we may not schedule additional servers for
  your
app,
  however.

  What leads you to conclude that your app is being throttled?

  -Nick Johnson

  On Tue, Sep 14, 2010 at 9:47 PM, Coding Social 
codingsoc...@gmail.comwrote:

   Hi,

   I have had appid mapthislink for many months now.  Recently my
   extensions that use this web service to unwind urls have been
featured
   by Google Chrome and Apple Safari so usage is up substantially.

   Can someone turn off the throttle?  Causing

[google-appengine] Re: Rolling back the update. java.lang.RuntimeException: Version not ready.

[bFlood]

seeing the same thing with Python...

On Sep 12, 12:45 pm, Jeff Schwartz jefftschwa...@gmail.com wrote:
 Unable to upload new version. Google App Engine System Status page indicates
 everything ok. Is there an issue?

 Creating staging directory
 Scanning for jsp files.
 Scanning files on local disk.
 Scanned 250 files.
 Scanned 500 files.
 Initiating update.
 Cloning 126 static files.
 Cloned 100 files.
 Cloning 406 application files.
 Cloned 100 files.
 Cloned 200 files.
 Cloned 300 files.
 Cloned 400 files.
 Uploading 5 files.
 Uploaded 1 files.
 Uploaded 2 files.
 Uploaded 3 files.
 Uploaded 4 files.
 Uploaded 5 files.
 Initializing precompilation...
 Deploying new version.
 Will check again in 1 seconds.
 Will check again in 2 seconds.
 Will check again in 4 seconds.
 Will check again in 8 seconds.
 Will check again in 16 seconds.
 Will check again in 32 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Will check again in 60 seconds.
 Rolling back the update.
 java.lang.RuntimeException: Version not ready.

 Debugging information may be found in
 C:\Users\Jeff\AppData\Local\Temp\appengine-deploy8427291715644717017.log

 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-appeng...@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: How to write a C# client to access google app engine?

[bFlood]

here's a decent example of how to use C# to authenticate using Google
ClientLogin. There enough code in there to see how you would GET/POST
against HTTP endpoints as well
http://dalelane.co.uk/blog/?p=894

we use C# (but any language would do) for our client libraries and
bulkloader and its been working great

cheers
brian


On Aug 18, 5:51 am, Vassili vassi...@gmail.com wrote:
 I do understand how browsers work:)
 Unfortunately the request sent by the web browser is quite hidden by
 Google App Engine plugin in all the html/java script unfriendly
 looking files it creates for you.
 I even do not know the name of the parameter of this default google
 app engine project.
 What I am asking is not a program in C#, but a simple concrete example
 in ANY language for sending this POST request in any format you wish.
 Interpreting the returned results is not needed (but details are
 important, like the parameter name).

 Thanks,
 Vassili

 On Aug 18, 5:29 am, Greg g.fawc...@gmail.com wrote:



  You need to understand how browsers work - in a nutshell, they send a
  request for a URL, and the server returns data. In most cases this
  data is HTML code to be rendered by your browser, but you can in fact
  make it anything you want - XML, JSON or a custom data format.

  Your C# application needs to be able to make an HTTP request to your
  URL, and then interpret the returned data. I don't know C# at all, but
  it must contain components to do the request part of this. That leaves
  you to add code to do whatever it is you want to with tee returned
  data.

-- 
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-appeng...@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: Update on Alfred Fuller's Next gen queries talk + geolocation

[bFlood]

i don't think there is marc but I agree, there's a lot to be excited
about based on that video

i had some comments on how it applied to geo queries here:
http://bit.ly/bDRPU7

cheers
brian

On Aug 2, 9:01 am, Marc Hacker marc1hac...@gmail.com wrote:
 Is there any update and ETA on the exciting new features previewed
 herehttp://code.google.com/events/io/2010/sessions/next-gen-queries-appen...

 Any advice how to prepare for this? For examples Alfred said there
 will be special queries for geolocation. Is there a specific format in
 which to store longitude/latitude today so that those queries will run
 on my data in the future?

 Any update when we might be able to query to number ranges?

 Thanks

 Marc

-- 
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-appeng...@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: I can see some of my source code files with Appstats

[bFlood]

I'm pretty sure only admins can see appstats but if that's not enough,
you can alter the main appstats handler to only accept a specific user
(I did this for our app). Drilling into the source is sometimes pretty
helpful

I do agree that somewhere in the appstats docs they should mention
leaking source code.

cheers
brian

On Jul 29, 4:07 am, Albert albertpa...@gmail.com wrote:
 Hi!

 I just wanted to bring it up again.

 I can see some of my source code files with Appstats.

 Most of which are the python files in my application.

 Is this expected functionality?

 Thanks!

 On Jul 23, 9:13 am, Albert albertpa...@gmail.com wrote:



  I can see some of my source code files with Appstats.

  Most of which are the python files in my application.

  Is this expected functionality?

-- 
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-appeng...@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: Latency

[bFlood]

great questions colin, I'd like to see the answers as well. I've seen
the exact same latency issues and I'm pretty sure there was a previous
thread talking about the same thing. it was from a couple months ago
so there we're no ms_pending headers to look at but it was related to
mysterious latency outside of a cold startup and user code execution,
so somewhere in the google infrastructure

cheers
brian


On Jul 28, 6:06 am, hawkett hawk...@gmail.com wrote:
 Hi,

    In the discussion below I am only referring to requests that did
 *not* start a new server instance, I'm comfortable with the fact that
 timings on these are all over the place.  It's the standard request
 processing I am looking at.  I'm using python and initiating requests
 from the UK.

    It was recently announced that app engine log timings now include
 latency, and I think I can see that in my apps logs. As a general
 rule, I try to keep the real-time activity of a single request below
 100ms. I judge whether I am achieving that based on the time between
 my app's 'Request Received' log message, and it's 'Sending Response'
 log message.

    One problem with this approach is that quite often I am seeing the
 total time on these requests up around 700 - 800 ms or more.  The
 first thing to note is that sometimes the difference between the time
 on Google's log header and my 'Request Received' log message is over
 500ms. e.g.

 07-28 02:08AM 26.148 /MyURL 200 793ms 127cpu_ms 30api_cpu_ms 3kb user
 agent  headers  stuff
 a.b.c.d - - [28/Jul/2010:02:08:26 -0700] GET /MyURL HTTP/1.1 200
 3646 http:/my-app.appspot.com/ user agent  headers  stuff my-
 app.appspot.com ms=793 cpu_ms=128 api_cpu_ms=31 cpm_usd=0.004105
 pending_ms=428

 07-28 02:08AM 26.579 Handling Request...
 ...
 07-28 02:08AM 26.662 Sending Response...

 So it looks like the 'pending_ms' in the header measures this,
 although this attribute is not always present in the log headers.  Is
 the occurrence of this something that we should expect fairly often
 going forward? Is the size of this number something that Google is
 trying to reduce?  It's a huge number for a web server.

 The second question is the difference between the total (793ms) and
 the log numbers.  26.148 - 26.662 = 514ms, so there's 279ms I'm
 trying to understand the cause of - its worth knowing too because it
 represents about 300% of my actual request handling time.  Sometimes
 this difference is as low as 20ms (for a similarly sized response), so
 it would appear to be something in google's infrastructure rather than
 raw network latency. What sort of things are we looking at here?

 I guess I'm asking this stuff because I've made a fair effort to
 reduce the request processing times on my app, but apart from billing
 advantages (user experience is far more important), this is largely
 irrelevant in the face of such huge overhead.  Is the size of this
 overhead something that google considers important to reduce - is it
 something you think can be reduced in the future, or should we expect
 requests to often incur 700%+ overhead on a warm server?

 I recognise that google would appear to be doing well here 
 -http://www.infoq.com/news/2010/07/Benchmarking-5-Cloud-Platforms,
 although the tests seem to be for static files, which I agree are
 served very quickly. It would be interesting to see the numbers for
 actual app requests to these platforms. I can see people consuming
 that graph and thinking 'Wow, my app's gonna fly on app engine'.

 Anyway, if you are able to shed any light on the current situation,
 and your hopes/expectations for the future, that would be much
 appreciated - cheers,

 Colin

-- 
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-appeng...@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: Questions concerning Datastore Growing Pains

[bFlood]

+1, well said.



On Jun 2, 7:29 pm, Bill Edwards twmaf...@gmail.com wrote:
 I would personally like more information on these datastore growing
 pains.  As a startup, that has been strongly considering building
 solely on Google App Engine, we are very, very concerned with these
 instances of failure.

 If possible, can somebody from the GAE team give us information, on a
 technical level, about how serious these problems are, and how
 preventable they are in the future?  Is it possible that after these
 problems are fixed, that this will reoccur 2-3 times a year?  If so,
 how likely?  If not, why not?

 I think you all would be doing the community a huge service by giving
 us a realistic outlook on problems to come.  If we can't depend 99.9%
 on GAE right now, that is fine.  We will come back when you are
 ready.  But, as a startup building a business application, we can't
 risk these sort of downtimes.

 I look forward to a candid response.

-- 
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-appeng...@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: DeadlineExceeded on cold hits.

[bFlood]

+1

On Jun 2, 11:19 am, dloomer dloo...@gmail.com wrote:
 I've been seeing increased DeadlineExceededErrors, and suspecting that
 it's an issue outside of my app but not sure.  I'm not sure if a three-
 post thread of somewhat similar experiences proves anything or not;
 when you refer to the increasingly poor datastore performance is
 this something that's documented elsewhere and/or acknowledged by
 Google?  I haven't been able to find anything so far indicating a bona
 fide known issue, but maybe I'm not looking in the right place.

 On Jun 1, 9:21 pm, Brandon Thomson gra...@gmail.com wrote:



  Yes, we are also seeing this. Usually the call at the end of the
  traceback is something related to the filesystem. I think this is
  caused by the increasingly poor datastore performance.

  On Jun 1, 6:16 pm, Dave Peck davep...@gmail.com wrote:

   Hi,

   In the past week, I've seen an alarming number of DeadlineExceeded
   exceptions on cold hits to my applications.

   Most of the stack traces are shallow -- things blow up well before my
   code is hit. Seehttp://pastie.org/988269forastack trace.

   The `bootstrap.py` file is more-or-less a direct copy of the `main.py`
   from Rietveld.

   Can someone on the App Engine team please point me in the right
   direction here? This is a big change in GAE's behavior in the past
   week, and it is affecting many of my applications (citygoround which
   has been in production for half a year; code-doctor which is under
   development, etc.)

   Cheers,
   Dave Peck- Hide quoted text -

  - Show quoted text -

-- 
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-appeng...@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: Query Latency, etc

[bFlood]

agreed, that's the worst Query latency graph I've ever seen

i really hope the answer to all of this doesn't come down to: buy GAE
for Business, it has an SLA



On Jun 1, 3:25 pm, James jamesk...@gmail.com wrote:
 Bay - Well put.

 Query latency status page is nearly all red today.  Same on Sunday.

 Ikai - A little transparency would go a long way here.  Can you
 oblige?

 On May 28, 12:39 pm, Bay troels...@gmail.com wrote:



  There just needs to be more information. This is a service people pay
  money for. Where are the explanations of todays errors? Adding an
  issue at the tracker almost always goes unnoticed - writing in these
  (three different) forum groups almost always goes unnoticed.

  Can we expect these 500 error that have been coming and going for
  months to be fixed one day, or are we supposed to pull our apps and
  rewrite them into something that is less scalable but -actually-
  working? This is not supposed to be hard. Everybody are confined to
  java and python - nothing more, errors can be contained. No
  filesystem, everything in a database which prohibit any operation that
  look like join and has indexes for everything that can be fetched
  except if one actually knows the unique key. With this in mind, things
  are simple. Its not supposed to be that hard - if you can't do what
  companies that allow SQL and multiple languages can, then please buy a
  hosting company and get some best practices from there. You've got the
  money - you've got our money, as we pay for the service. If you need
  more money to make it work upp the prices a little, because -random-
  500 errors are unacceptable for everybody.

  A few answers and a few pieces of information would be nice. Thank
  you.

  On May 28, 6:04 pm, Millisecond millisec...@gmail.com wrote:

   The querylatencyhas been red on and off all morning, requests are
   returning 500's and not counting as errors (saw another thread I was
   going to reference about other people seeing this as well, but can't
   find it now), but no alerts/status 
   updates:http://code.google.com/status/appengine/detail/datastore/2010/05/28#a...

   The only day marked as 'service disruption' was May 25th, but we've
   thrown 75,000+ errors in the past week due tolatency, not including
   May 25th.

   Billing is missing and no word from Google on whether it's
   intentional:http://groups.google.com/group/google-appengine/browse_thread/thread/...

   Would be great to hear about how this is all just a temporary thing,
   what the problem is, and what Google's plan is to fix it.  But, at the
   moment, this feels like normal operation of AppEngine and nobody at
   Google is concerned which really has me concerned.

   -C

-- 
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-appeng...@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: Interesting evaluation of AppEngine for transaction processing and a comparison to other cloud providers

[bFlood]

hi ivan

when will the new GAE results using non-transactional writes be
available? also, were these tests run *after* the 500 rps limit was
removed?

at first glance, it looks like a pretty thorough test and GAE does not
look too good...

thanks
brian

On May 27, 7:27 am, Ivan Zuzak izu...@gmail.com wrote:
 Hi all,

 Just thought I'd mention this here as it is probably interesting to
 AppEngine developers -- there's a paper on An Evaluation of
 Alternative Architectures for Transaction Processing in the Cloud
 available at [1] and a short overview at [2].

 Best,
 Ivan

 [1]http://systems.ethz.pubzone.org/servlet/Attachment?attachmentId=76ve...

 [2]http://highscalability.com/blog/2010/5/26/end-to-end-performance-stud...

-- 
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-appeng...@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: Task queue can't keep up with load. Suggestions?

[bFlood]

i agree waleed. ever since the 500 request/second limit was removed
from GAE about a month ago, the Task queue has taken a pretty big hit.
When they raised the queue limit to 40/sec it was flying but then the
limit above was removed (a good thing!) and the amount of 500 errors
in the queue went through the roof. I can't even come close the
incredible performance I saw originally. Google told me to just make
sure all tasks ran below 1 second but this doesn't even really help
and IMO, defeats one of the main goals of the Task Queue itself
(longer running processing, albeit below 30 secs)

brian



On May 21, 2:00 pm, Waleed Abdulla wal...@ninua.com wrote:
 It seems that the speed at which the task queue executes tasks is not
 catching up to how fast I'm inserting tasks to it. See attached screen: the
 feed-pulls task is set to a rate of 25/second and a bucket size of 20 (the
 max allowed). I'd expect to see an execution rate of 1500 tasks per minute
 or close to that, but instead it's running at a rate of about 400 tasks per
 minute. As a result, the queue keeps getting longer (I have tasks that are 3
 days old still waiting to execute).

 What can I do about this?

 Regards,
 Waleed

 --
 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-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to 
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group 
 athttp://groups.google.com/group/google-appengine?hl=en.

  Screen shot 2010-05-20 at 5.11.16 PM.png
 30KViewDownload

-- 
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-appeng...@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: App Engine For Business

[bFlood]

with the current information on this topic, I feel a little uneasy as
well.

there was a Google Wave from AppEngine fireside chat yesterday that
had some more info (can't find link anymore). from memory, please
correct if I've got it wrong:

when asked about AEfB and regular GAE, one answer was that they are
firmly committed to parity between the two. no details given except
one said AEfB was for intranet usage

when asked if GAE would get SSL they answered that AEfB would handle
that and would have some form of pricing for internet users. I didn't
get the sense that SSL or an SLA were coming to GAE (from the limited
info on the wave)

this should be easy for Google to clear up. I think everyone can see
the benefit of a different pricing model for enterprise users and I
think per user pricing is great for a lot of apps. however, the real
question is whether regular GAE is going to get SSL, an SLA, and
access to the new SQL service. if the answer is no, then this is just
a business decision by google to force potential enterprise clients
into a per user model (which IMO is a bad idea, there should be a
clear choice fro pricing models). please clear this up google, you're
making a lot of your early adopters anxious :)

cheers
brian






On May 20, 6:09 am, Jesaja Everling jeverl...@gmail.com wrote:
 According to the FAQ, per user really means per intranet user here:

 You can also use App Engine for Business to build external applications.
 We’re still working out the details on pricing so stay tuned (but don’t
 worry, you won't have to pay per 
 user!).http://code.google.com/appengine/kb/business.html

 It seems to be more like a special version of App Engine intended for (not
 only) internal use by Google Apps customers.
 If this is right, it sounds good.
 If it were to introduce some artificial segmentation and the regular App
 Engine were to become some strip-down limited version of App Engine for
 Business, it wouldn't sound good at all.
 But this would be a bad move, and it seems Google is more in the mood for
 good moves at the moment ( VP8 :) ).

 On May 20, 2010 4:40 AM, Shinichi Nakanishi stouton...@gmail.com wrote:

 Yes, if it was Google Apps, it would make sense.  But for App Engine,
 I don't think per user registered in the Apps domain thing works.
 For instance, what if you do not register your domain but use
 your-subdomain.appspot.com?  Is it $0 and still be able to use
 features like Hosted SQL?

 So, I have no idea what per user here means.

 Shinichi

 On Wed, May 19, 2010 at 18:39, Geoffrey Spear geoffsp...@gmail.com wrote:

  On May 19, 6:00 p...

 --
 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-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to 
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group 
 athttp://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-appeng...@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: App Engine For Business

[bFlood]

i found the Wave here: http://bit.ly/9soPI1

and here was one of the puzzling answer I remembered:
Q: AEfB will support SSL for top-level domains.  Will this be
available for non-enterprise (public) apps?
A: Yes.  There will be a part of AEfB that you can use outside of a
company.  The pricing of these features may be different; we're still
figuring that out.

maybe the Google guy just misheard him but I thought he was asking if
regular GAE apps will get SSL for top-level domains.

cheers
brian


On May 20, 8:32 am, gops patelgo...@gmail.com wrote:
 why not just introduce, SQL as a additional api along with datastore
 and blobstore as sqlstore with different costing model ? , and there
 is already plenty of way to connect to google apps , why not just add
 SLA as one more option instead of creating whole new AEfB , and while
 already charging for users already via google apps, why should charge
 them again for each individual app ? , pay as much as you use is
 pretty beautiful model please please stick to it, even thou we
 developers are not enterprise, our clients are enterprise. and we love
 to see they are using google apps.

 On May 20, 5:06 pm, bFlood bflood...@gmail.com wrote:





  with the current information on this topic, I feel a little uneasy as
  well.

  there was a Google Wave from AppEngine fireside chat yesterday that
  had some more info (can't find link anymore). from memory, please
  correct if I've got it wrong:

  when asked about AEfB and regular GAE, one answer was that they are
  firmly committed to parity between the two. no details given except
  one said AEfB was for intranet usage

  when asked if GAE would get SSL they answered that AEfB would handle
  that and would have some form of pricing for internet users. I didn't
  get the sense that SSL or an SLA were coming to GAE (from the limited
  info on the wave)

  this should be easy for Google to clear up. I think everyone can see
  the benefit of a different pricing model for enterprise users and I
  think per user pricing is great for a lot of apps. however, the real
  question is whether regular GAE is going to get SSL, an SLA, and
  access to the new SQL service. if the answer is no, then this is just
  a business decision by google to force potential enterprise clients
  into a per user model (which IMO is a bad idea, there should be a
  clear choice fro pricing models). please clear this up google, you're
  making a lot of your early adopters anxious :)

  cheers
  brian

  On May 20, 6:09 am, Jesaja Everling jeverl...@gmail.com wrote:

   According to the FAQ, per user really means per intranet user here:

   You can also use App Engine for Business to build external applications.
   We’re still working out the details on pricing so stay tuned (but don’t
   worry, you won't have to pay per 
   user!).http://code.google.com/appengine/kb/business.html

   It seems to be more like a special version of App Engine intended for (not
   only) internal use by Google Apps customers.
   If this is right, it sounds good.
   If it were to introduce some artificial segmentation and the regular App
   Engine were to become some strip-down limited version of App Engine for
   Business, it wouldn't sound good at all.
   But this would be a bad move, and it seems Google is more in the mood for
   good moves at the moment ( VP8 :) ).

   On May 20, 2010 4:40 AM, Shinichi Nakanishi stouton...@gmail.com 
   wrote:

   Yes, if it was Google Apps, it would make sense.  But for App Engine,
   I don't think per user registered in the Apps domain thing works.
   For instance, what if you do not register your domain but use
   your-subdomain.appspot.com?  Is it $0 and still be able to use
   features like Hosted SQL?

   So, I have no idea what per user here means.

   Shinichi

   On Wed, May 19, 2010 at 18:39, Geoffrey Spear geoffsp...@gmail.com 
   wrote:

On May 19, 6:00 p...

   --
   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-appeng...@googlegroups.com.
   To unsubscribe from this group, send email to 
   google-appengine+unsubscr...@googlegroups.com.
   For more options, visit this group 
   athttp://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-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to 
  google-appengine+unsubscr...@googlegroups.com.
  For more options, visit this group 
  athttp://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-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to 
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group

[google-appengine] Re: Per-domain data stores and selling our apps to people who use google domains...

[bFlood]

this is a great idea, starred.

right now we deploy our app to each user's GAE instance somewhat
manually. it's not too difficult with a limited number of clients but
an automated method using a Google sanctioned app store would be
great.

cheers
brian

On May 7, 7:23 am, Stephan Hartmann hartm...@metamesh.de wrote:
 Hi Andy,

 In general i like your idea and i stared it.

 Do i understand it right, that you could already achieve this, if every
 customer would have its own GAE account and deploy your app to it and add it
 to his apps domain?
 You just want to make this process a one-click-buy in the Google
 marketplace?
 Then it should be also possible to update the applications via marketplace
 in case there is a new version.

 But you should still have the choice to offer an app also as one-for-all
 with real multi-tenancy support.

 Regards,
 Stephan

 2010/5/6 Andy Burke abu...@bitflood.org





  Hi,

  My name is Andy Burke.  I have a background in the video game
  industry, but I also dabble in GAE.  About a year ago I got excited
  about developing a GAE-based issue tracker.  GAE seems like the
  perfect platform for such an application.  I began working, got my
  issues into the datastore, got some rudimentary milestone support,
  email integration, all that jazz.  Then I started thinking about how I
  was going to roll this application out.  I realized that I'd need to
  add a lot of complexity to my data model to keep different 'domains'
  separate (a domain being something like a company who can have any
  number of projects in the system).  Additionally, I'd end up, as the
  developer of the application, with access to all these different
  domains' data.  Why would a company want to use my issue tracking
  software if they knew I could gain access to all their internal
  issues?  I'm just some guy off the street, I'm not Google, why should
  they trust me?

  After thinking about all this, I opened an issue w/ GAE:

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

  The features I'm effectively asking for in the issue are:

  - Each google apps domain should have its own datastore
  - Each google apps domain should be able to install an app created
  with GAE into its own domain

  Now, this seems like it would be great for developers and great for
  Google:

  - It would make it a lot easier to develop apps that might be used by
  lots of different organizations, simplifying GAE developers' datastore
  models
  - It would mean that billing for application usage could be per-domain
  in addition to per-app
   - Eg: if I make a really popular app, I don't have to pay google for
  the bandwidth and storage, the domains that install and use it do
  - Google could build out a way that GAE-developed apps could be
  installed into domains with various pricing models:
   - One-time cost
   - Subscription based
   - Per-transaction
  - Google could skim money off the top, the rest would be passed on to
  the app developer, ala the iPhone App Store or Facebook credits

  Let me give you a little imaginary scenario that demonstrates what I'd
  like to see happen with GAE:

  I develop my issue tracking software and it's really nice.  I set my
  app up to use per-domain datastores.  I also set my app to be
  available for a monthly subscription of $10, with the first month
  free.  So now people who use Google apps for their domains can install
  my app into their domain and try it out for the first month.  If they
  want to keep using it, they'll start paying $10/month through Google
  checkout (or whatever service Google provides).  All their issues are
  stored in their own domain.  Even as the developer, I don't have
  access to them and they don't have to worry about privacy issues from
  me.  If they generate a ton of datastore queries because they're a
  huge company, they get billed for that, not me.  Google takes their
  cut from the subscription payment, say 30%.  Google's happily getting
  $3/month for each domain using my app.  I'm happily getting $7 a month
  and not worrying about the datastore for all these different
  companies.  The company that's using my app is happy because their
  data is all private.  They're also really happy they hosted with
  Google apps because they realize they have access to tons of software
  as a service that's easy to install in their domain, maintains their
  privacy and adds value to using Google apps.

  This seems like such a huge win for Google, GAE developers and Google
  Apps customers: why has this issue been languishing for over a year?

  I'd really love to hear if these features have any chance of being
  implemented.  I haven't done much on GAE with regard to apps that
  could be used as SaaS in the last year because it seems so daunting to
  handle the datastore/bandwidth usage costs of GAE, the separation of
  data by domain, the amount of work I'd need to do to be able to bill a
  domain for their usage, etc.  It seems like 

[google-appengine] Re: Request was aborted after waiting too long

[bFlood]

my task queue is filled with these today. each task had been paired
back to 20 small entity puts.



On May 6, 11:42 am, mkmanning michaell...@gmail.com wrote:
 One of my apps started getting this yesterday and the problem
 continued all day, and is still there this a.m. This is happening any
 time you visit the app. The error log for / shows:

 Request was aborted after waiting too long to attempt to service your
 request. This may happen sporadically when the App Engine serving
 cluster is under unexpectedly high or uneven load. If you see this
 message frequently, please contact the App Engine team.

 This started after my app had been up and running for months, with no
 changes; worked the day before, then dead.

 Nothing in the system status shows what the cause may be or what (if
 anything) is being done about this.

 On May 5, 12:56 pm, bsb b...@pearcomp.com wrote:





  I also get the same error with cron jobs in another app of mine. This
  has only started happening recently. Can someone @ Google please take
  a look at this?

  On May 5, 10:18 am, Benjamin Schuster-Böckler b...@pearcomp.com
  wrote:

   I'm getting loads of these. It's ok with the deferred tasks, as they are 
   rescheduled, but the cron jobs (to be run every 10min) just don't run if 
   this happens, causing unpredictable behaviour of my app. Effectually, the 
   cron only runs eery few hours, because most of the time, this error 
   occurs. What can I do to fix this? Do I really need to have a dummy task 
   to constantly hammer instances so the app stays loaded?

   Thanks in advance,
   Ben

   --
   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-appeng...@googlegroups.com.
   To unsubscribe from this group, send email to 
   google-appengine+unsubscr...@googlegroups.com.
   For more options, visit this group 
   athttp://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-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to 
  google-appengine+unsubscr...@googlegroups.com.
  For more options, visit this group 
  athttp://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-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to 
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group 
 athttp://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-appeng...@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] Query Latency today

[bFlood]

any word on the cause? is it related to the planned maintenance today?
http://code.google.com/status/appengine/detail/datastore/2010/04/28#ae-trust-detail-datastore-query-latency

every 3rd or 4th query is well over 1000ms...

cheers
brian

-- 
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-appeng...@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: 'Simultaneous Active Requests' limit really needs clarifying!

[bFlood]

this is exactly what I'm seeing with the Task Queue as of yesterday.
it was ripping fast 2 days ago, I was getting close to 150 features/
second upload/index. now this has dropped considerably and there are
many timeouts on the TQ after only 10secs (startup time, not even
hitting my code).

http://groups.google.com/group/google-appengine/browse_thread/thread/85dc115fac469b21#





On Apr 16, 10:20 am, hawkett hawk...@gmail.com wrote:
 Hi Nick,

    This is a little disconcerting - would it be fair to say that if I
 were using the pattern you documented 
 herehttp://code.google.com/appengine/articles/deferred.html,
 then my latencies would not be low (since I am pushing the
 DeadlineExceededError on every deferred operation), and my app will
 become request limited? Perhaps this pattern should be processing only
 one or two records at a time (and then risking the task limit)?
 Perhaps it does not apply to requests initiated from the task queue?
 Would be good to get some clarification on what we can and can't do.
 Cheers,

 Colin

 On Apr 10, 4:18 pm, Nick Johnson (Google) nick.john...@google.com
 wrote:





  Hi Peter,

  The simultaneous dynamic request limit was eliminated in a recent SDK. It
  has been replaced with the flexible provisioning system detailed in the FAQ
  entry you quote.

  It's correct that as long as you keep your latencies low, you should never
  run into any sort of request limit.

  -Nick Johnson

  On Sat, Apr 10, 2010 at 2:12 PM, peterk peter.ke...@gmail.com wrote:
   I've been using and watching appengine since, well, the beginning, and
   only by a random Google about an unrelated topic did I find out about
   this notion of a cap on 'simultaneous active requests'.  I came across
   discussions where people were saying that there is a cap of 30
   simultaneous active requests, citing the Quota page and so on.

   But when I go to the Quota page - there's not a single mention of any
   such limit. Why not? Has something changed?

   Reading the quotas on that page it's easy to conclude - naively
   perhaps in hindsight - that 500 requests/second is 500 requests/second
   irrespective of the average execution time of those requests.

   There is no mention of any assumption on that page about the time
   taken to serve a request or anything else that goes into the
   calculation for 500 requests/second.

   After some further searching I finally found mention of this limit in
   the FAQs, but here it's still quite vague - and again, no specific
   mention of this 30 simultaneous request limit. It says:

   However, App Engine reserves automatic scaling capacity for
   applications with low latency, where the application responds to
   requests in less than one second. Applications with very high latency
   (over one second per request for many requests) are limited by the
   system, and require a special exemption in order to have a large
   number of simultaneous dynamic requests. If your application has a
   strong need for a high throughput of long-running requests, you can
   request an exemption from the simultaneous dynamic request limit. The
   vast majority of applications do not require any exemption.

   Which doesn't imply a hard limit, but rather that as long as your
   (average?) request fulfilment time is below one second you shouldn't
   have to worry about this. To be very exacting, if I keep my average
   request time under 1 second I should *never* see an error relating to
   this cap? This is a bit different than the talk of 30 simultaneous
   requests max - at that level with the max of 500 requests a second,
   you'd be limited to an average request time of 60ms!

   So what is the story here? Why is this all being talked about in the
   shadows of message boards with no clear policy? Why isn't this
   limitation in the quota page? I thought I had GAE all figured out but
   then this ball gets thrown into the mix out of left field.

   --
   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-appeng...@googlegroups.com.
   To unsubscribe from this group, send email to
   google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2Bunsubscrib
e...@googlegroups.com
   .
   For more options, visit this group at
  http://groups.google.com/group/google-appengine?hl=en.

  --
  Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. ::
  Registered in Dublin, Ireland, Registration Number: 368047
  Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
  368047

 --
 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-appeng...@googlegroups.com.
 To unsubscribe from this group, send email to 
 google-appengine+unsubscr...@googlegroups.com.
 For more options, visit this group 
 athttp://groups.google.com/group/google-appengine?hl=en.

[google-appengine] task queue timeouts

[bFlood]

is anyone else seeing a lot more Task Queue 10 seconds timeouts today?
These tasks usually take about 10-15secs to complete and were running
really fast yesterday. Billing enabled.

Request was aborted after waiting too long to attempt to service your
request. 
/tasks/indexing 500 10026ms 0cpu_ms 0kb AppEngine-Google; (+http://
code.google.com/appengine)
0.1.0.2

-- 
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-appeng...@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: task queue timeouts

[bFlood]

thx james, I saw that issue# and had starred already

1) this was just working yesterday
2) has the Task Queue been depreciated in favor of some (future)
background worker scenario? (see last comment on that issue link). I'm
in favor of this but it would be nice if that were available before
they started throttling the TQ
3) I wonder if this is related to the removal of the Simultaneous
Requests limit (http://code.google.com/appengine/kb/
general.html#activerequests) which seems to favor low latency request
and penalizes long running ones (although if this is the case, I'm not
how anyone can do anything meaningful with  the Task Queue)


cheers
brian

On Apr 15, 3:00 pm, James jamesk...@gmail.com wrote:
 Star this puppy 
 -http://code.google.com/p/googleappengine/issues/detail?id=2396

 On Apr 15, 11:39 am, bFlood bflood...@gmail.com wrote:



  is anyone else seeing a lot more Task Queue 10 seconds timeouts today?
  These tasks usually take about 10-15secs to complete and were running
  really fast yesterday. Billing enabled.

  Request was aborted after waiting too long to attempt to service your
  request. 
  /tasks/indexing 500 10026ms 0cpu_ms 0kb AppEngine-Google; (+http://
  code.google.com/appengine)
  0.1.0.2

-- 
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-appeng...@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: Request per Second limitation (PLEASE)

[bFlood]

hi nick

great news. how often is this average calculated? do large bulk
uploads or periodic task queue runs that consume a lot of CPU time
factor into this?

cheers
brian

On Apr 14, 1:21 pm, Nick Johnson (Google) nick.john...@google.com
wrote:
 Hi Jairo,

 If your average latency is low (below 1 second), you should be able to scale
 up to any request load, as long as you provide the budget to support it.

 -Nick Johnson

 On Wed, Apr 14, 2010 at 5:37 PM, Jairo Vasquez jairo.vasq...@gmail.comwrote:





  Hi,

  I am managing 650 request per second. Can I start to manage 1200
  request per second?

  I need to know what my limits are, what can I do.

  Should I use another solution or can GAE support this load?

  Thanks

  --
  Jairo Vasquez Moreno
  Mentez Developer
 www.mentez.com
  Medellin - Colombia

  --
  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-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to
  google-appengine+unsubscr...@googlegroups.comgoogle-appengine%2Bunsubscrib 
  e...@googlegroups.com
  .
  For more options, visit this group at
 http://groups.google.com/group/google-appengine?hl=en.

 --
 Nick Johnson, Developer Programs Engineer, App Engine Google Ireland Ltd. ::
 Registered in Dublin, Ireland, Registration Number: 368047
 Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number:
 368047

-- 
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-appeng...@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: 'Simultaneous Active Requests' limit really needs clarifying!

[bFlood]

I'm also interested in how this works. bump

On Apr 11, 2:15 am, Brandon Thomson gra...@gmail.com wrote:
 I am curious about how this works too. I've bumped up against this
 limit in the past when the datastore is acting up and rpcs start
 taking multiple seconds to return.

-- 
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-appeng...@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: GAE and Apps Marketplace

[bFlood]

the new RoadMap looks awesome. thanks google.

On Mar 26, 12:58 am, Rajkumar Radhakrishnan r.rajku...@gmail.com
wrote:
 Now we can focus more on our app's value-add.
 Thank you, App Engine people at Google !!

 And to you too, Roberto Saccon for sharing the news with this group.

 Regards,
 R.Rajkumar





 On Fri, Mar 26, 2010 at 5:41 AM, Roberto Saccon rsac...@gmail.com wrote:
  Native support for oAuth / openid is coming:
 http://code.google.com/appengine/docs/roadmap.html

  On Mar 25, 9:19 am, pca pierre.carbonne...@gmail.com wrote:
   I fully support the suggestion that GAE's authentication library
   should allow integration in Google Marketplace out-of-the-box.
   Actually, I'm eagerly waiting for this to happen.  I won't try to do
   such integration for my python GAE apps myself: it just seems too
   difficult.

   PC

   On Mar 12, 3:54 am, Rajkumar Radhakrishnan r.rajku...@gmail.com
   wrote:

Hi Guys,

While there seems to be this related thread on the forum Ikai Lan has
mentioned, which you may follow / add to the thread as need be..
 http://www.google.com/support/forum/p/apps-apis/thread?tid=52e36f012c...

..I think our options for the moment are pretty clear.

For developers over Google App Engine, I think the current option is
to support OpenID and then list yourself in the Google Marketplace.

Nicholas Johnson's AEoid http://github.com/Arachnid/aeoid seems to
  be
a good place to start. You may want to check out Evan Kaufman's
forkhttp://github.com/EvanK/aeoidwhich include many useful changes
and Scott
Ellis' fork http://github.com/sje397 which include Evan's changes
  and a
little more (in contains some of his specific code too, which you might
  want
to update). I tested Scott's fork and it seems to work fine in my
development environment. But, my concern is should this not be part of
Google App Engine itself ?

In could be better if OpenID support was by default available (may be
  as a
deployment option) in Google App Engine, instead of each one of us
  having to
integrate a package which we think is good and that which also includes
session maintenance.

Once this OpenID support is included in default Google App Engine, it
  is
easier for existing apps to adapt to the authentication mode and then
  list
themselves in the marketplace. So, this is for App Engine guys at
  Google to
decide.

Another way in which App Engine people at Google can help is to provide
  a
click to install option. This will require very minimal changes to
  the
existing apps. In this approach applications can be marked for sale -
  may be
from the apps dashboard by the developer, and can redeployed to a
  customer's
App Engine account, after the customer has paid for the same via
  Google. Of
course, such redeployed apps cannot be resold, from that apps
dashboard. Google can take a cut from the recurring/one-time sale
proceedings and also by enabling billing for those customers.

Come on App Engine guys, help us and help yourself make some money. We
  are
already betting on you.

Thanks  Regards,
R.Rajkumar

On Fri, Mar 12, 2010 at 12:25 AM, Ikai L (Google) ika...@google.com
  wrote:

 Can you guys also ask here?

http://www.google.com/support/forum/p/apps-apis?hl=en

 I apologize if it seems like I'm punting the question a bit, but this
 really isn't a subject I have much familiarity with. Trying to keep
  up
 with all the different Google APIs is more than a full-time job in
  and
 of itself =).

 On Thu, Mar 11, 2010 at 9:42 AM, Jérémy Selier 
  jerem.sel...@gmail.com
 wrote:
  I'm interested too. I've tried using with
http://openid-consumer.appspot.com/
  andhttps://www.google.com/accounts/o8/site-xrds?hd=mydomain.comand
  this seems to not working.
  I think that we have to use some custom version of the openid
  consumer
  lib to be able to deal with OpenID Google Apps discovery.

  --
  Jeremy

  On Mar 11, 3:51 pm, Wooble geoffsp...@gmail.com wrote:
  You can only have your app authenticate to a single apps domain,
  and
  you have to choose that domain when you create the application.
   This
  makes it kind of impossible to sell integration to a google apps
  domain you weren't aware of when you wrote the app, let alone 2 or
  more of them.

  On Mar 11, 7:08 am, Tim Hoffman zutes...@gmail.com wrote:

   Hi

   I don't think you would need it.  An app engine app can already
  use
   the apps domain to authenticate.
   That page you are referring to is for applications not running
  in app
   engine (say on ec2, that want to use the users google apps
  account to
   login to that third party service).

   By the way there are a few libraries out there for python.

   T

   On Mar 11, 10:52 am, molicule molic...@gmail.com wrote:

 

[google-appengine] Re: Pre-release 1.3.2 SDKs available

[bFlood]

agreed, some great stuff in there! congrats!

On Mar 17, 5:39 am, George  Moschovitis george.moschovi...@gmail.com
wrote:
 Seems like a *great* release!

 -g.

 --http://www.appenginejs.org

 On Mar 17, 9:07 am, Tristan tristan.slomin...@gmail.com wrote:



  App Engine Java SDK - Release Notes

  Version 1.3.2
  =
  - New API to read the contents of uploaded Blobs (fetch_data)
     http://code.google.com/p/googleappengine/issues/detail?id=2536
  - URLFetch now supports accessing ports 80-90, 440-450, and 1024-65535
  - Mail API now allows common document formats as attachments
     http://code.google.com/p/googleappengine/issues/detail?id=494
  - The Task Queue API now supports adding multiple tasks in a single
  call to
    Queue.add()
  - Fixed charset handling for inbound emails
     http://code.google.com/p/googleappengine/issues/detail?id=2326
  - Fixed issue with compositing background colors in dev_appserver
  - New feature in the datastore to specify whether to use strong or
  eventually
    consistent reads (the default is strong)
  - New datastore feature allows setting deadlines for operations
  - Increased the maximum Task Queue refill rate from 20/s to 50/s
  - Support for IP blacklisting to prevent denial of service (DoS)
  attacks
  - App Stats is now available for the Java SDK in addition to Python
  - Fix issue with expiration times not being reset on Put on the
  Memchache API
     http://code.google.com/p/googleappengine/issues/detail?id=1284
  - Fix issue preventing static files from being served when a servlet
  is mapped to root
     http://code.google.com/p/googleappengine/issues/detail?id=1379

  On Mar 16, 11:50 pm, mb doit...@gmail.com wrote:

   Wow, this is a substantial release!

   App Engine Python SDK - Release Notes

   Version 1.3.2
   =
   - New API to read the contents of uploaded Blobs (fetch_data)
      http://code.google.com/p/googleappengine/issues/detail?id=2536
   - URLFetch now supports accessing ports 80-90, 440-450, and 1024-65535
   - Mail API now allows common document formats as attachments
      http://code.google.com/p/googleappengine/issues/detail?id=494
   - The Task Queue API now supports adding multiple tasks in a single
   call to
     Queue.add()
   - Fixed charset handling for inbound emails
      http://code.google.com/p/googleappengine/issues/detail?id=2326
   - Fixed issue with compositing background colors in dev_appserver
   - New feature in the datastore to specify whether to use strong or
   eventually
     consistent reads (the default is strong)
   - New datastore feature allows setting deadlines for operations
   - Increased the maximum Task Queue refill rate from 20/s to 50/s
   - Support for IP blacklisting to prevent denial of service (DoS)
   attacks
   - Fix an issue with Mac Launcher in Mac OSX 10.5.5
      http://code.google.com/p/googleappengine/issues/detail?id=778
   - Fix issue with slow updates when there are many skipped files
      http://code.google.com/p/googleappengine/issues/detail?id=2492
   - Fix issue with cursor not updating when using a GqlQuery
      http://code.google.com/p/googleappengine/issues/detail?id=2757

   On Mar 16, 8:31 pm, Jason (Google) apija...@google.com wrote:

Hi Everyone. Just a quick note that we just uploaded pre-release 1.3.2
SDKs for Python and Java to our Google Code project page:

   http://code.google.com/p/googleappengine/downloads/list

Both pre-release SDKs include RELEASE_NOTE files that indicate what's
new, but the App Engine back-ends have not yet been updated, so please
don't try to use these new features in production just yet. Please
test your existing applications locally using the new SDK and report
any bugs as soon as possible. Our next general release will likely
follow in the next couple of weeks barring any unforeseen issues.

Thanks,
- Jason

-- 
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-appeng...@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: BlobProperty limit

[bFlood]

hello

maybe you should try 11 parts so each would be below the max 1MB api
limit. You definitely need separate entities for each part

I use this technique right now to store large images and it does work.
In the future, if Google adds a BlobStore api for manipulating large
files from your app code, you could switch over to that. until then,
you'll need to split them up or use an external service like S3
(although the 1MB limit on urlfetch makes this very difficult as well)

cheers
brian

On Mar 10, 2:51 am, Adhi adhi.ramanat...@orangescape.com wrote:
 Hi Barry,
 Thanks for your reply. I tried in 2 ways

 Split the data into 10 parts and
 1. Created separate entity for each part (as you told)
 2. In a single entity with 10 dynamic properties (since its not always
 10 parts might be less for some cases)

 In both ways I'm getting RequestTooLargeError: The request to API
 call datastore_v3.Put() was too large.
 when I try to put the entity(s) in a single db.put().

 So do I've to use separate db.put for each entity?

 Thankyou
 Adhi

 On Mar 2, 6:45 pm, Barry Hunter barrybhun...@googlemail.com wrote:



   Is it possible to increase thelimitforblobpropertysize upto 10 MB?

  no.

  Split the Blob and store in 10 Separate entities.

-- 
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-appeng...@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.

[appengine-java] Re: Task queue not starting the action when expected

[bFlood]

I'm seeing this in Python too, not sure when it started. I'm chaining
tasks together to loop over a large set of data so there is only one
task executing at a time. Some execute right after the previous one
completes (as expected and as it worked in the past) while others take
between 15-30 seconds to start. There are no TransientErrors being
throw and all the tasks have unique names.

Ikai - is capacity defined for each App or for GAE as a whole?

I starred the issue. IMO, this is not a small problem

thanks
brian

On Mar 7, 1:34 am, kazunori_279 kazunori...@gmail.com wrote:
 Hi,

 I've experienced the same phenomenon so that I added a new issue for
 this:

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

 Thanks,

 Kaz

 On Feb 26, 8:05 am, Jerome jerome.mou...@gmail.com wrote:



  Hello,

  We have been usingtaskqueues for a few months without problem. We
  handle actions that must execute right away.

  At the time of the release of 1.3.1, we noticed that sometimes, some
  tasks will take 1 to 2 minutes to start, but in thetaskqueue, the
  ETA shows as a date in the past (like 0:01:12 ago), usually 1 second
  or so after the creation time.

  This is not a consistent issue. I might works perfectly (taskbeing
  kicked in within 1 second of creation) for several times and suddenly,
  the nexttasktakes 1.5 minutes to get started.

  Ourtaskqueueis empty when we see this issue.
  Ourqueueis setup with a max rate of 5/s and a bucket size of 1.

  Any idea of what we can do to work around or solve this new issue?

  Jerome

-- 
You received this message because you are subscribed to the Google Groups 
Google App Engine for Java group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

[google-appengine] Re: Parallel access to appengine

[bFlood]

bump

On Mar 3, 7:23 pm, Eli Jones eli.jo...@gmail.com wrote:
 Heh, yes.. I printed out your Java and it seemed perfectly fine after
 reading through it several times... But Java is just wayy to busy
 looking for my tastes.

 Good luck getting some clarification on what's happening with this.

 On 3/3/10, Gary Orser garyor...@gmail.com wrote:



  Eli,

  Python as usual is sooo much more elegant than java.

  I confirmed your test results on a billing enabled appspot.

  Cheers, Gary

  On Mar 2, 9:57 pm, Eli Jones eli.jo...@gmail.com wrote:
  I did my own testing in python.  And, I definitely couldn't get 30
  simultaneous requests to work.

  This was done on a test app that does not have Billing Enabled.. so not
  sure
  if that affects the Dynamic Request Limit.

  Either way, it seems that for this test, the effective Limit was 16
  simultaneous accesses.  As soon as I modified my code to try 17, it
  started
  throwing a few  Dynamic Request Limit errors.. though, the Logs page
  AppEngine just refers to it as another Request (with code 500 and a time
  of
  10 seconds).

  Here is the code for the handler.. after receiving a GET, it sleeps for 3
  seconds and the responds with a 'hello':

  from google.appengine.ext import webapp
  from google.appengine.ext.webapp.util import run_wsgi_app
  import time

  class meTest(webapp.RequestHandler):
      def get(self):
          time.sleep(3)
          meid = self.request.get('id')
          self.response.out.write('hi! foo%s'%meid)

  application = webapp.WSGIApplication([('/test/meTest',meTest)],
                                       debug = True)

  def main():
      run_wsgi_app(application)

  if __name__ == __main__:
      main()

  And here is they python code I am running on my local machine to test.  It
  fires off 17 threads.  Each thread requests a GET from the handler and
  prints the response, three times in a row:

  import httplib
  import threading

  class meThread(threading.Thread):
      def run(self):
          for i in range(3):
              conn = httplib.HTTPConnection('datastoretester.appspot.com')
              conn.request(GET,/test/meTest?id=%s % self.getName())
              response = conn.getresponse()
              print response.read()
              conn.close()

  for i in range(17):
      meThread(name=str(i+1)).start()

  As soon as I scale the range back to (16), no more Dynamic Request Error.

  Special notes:  I am not sure if there is some sort of built in
  rate-limiting for requests from the same IP address.. but when sending 17
  threads at the handler.. it is not responding in 3 seconds to their GETs..
  It takes about 11 seconds.

  If you look in the Logs, for a run with 17 threads, you see this:

  03-02 08:31PM 00.384 /test/meTest?id=16 200 12855ms 19cpu_ms 0kb gzip(gfe)
  03-02 08:31PM 01.266 /test/meTest?id=7 200 11973ms 19cpu_ms 0kb gzip(gfe)
  03-02 08:31PM 01.283 /test/meTest?id=15 500 10017ms 0cpu_ms 0kb gzip(gfe)
  03-02 08:30PM 58.280 /test/meTest?id=4 200 11952ms 0cpu_ms 0kb gzip(gfe)

  (Notice the 500 error in there as well.. that's the one that mentions the
  Dynamic Request Limit).

  Now, if I run the test with only 4 threads, it looks nice and quick like
  this:

  03-02 08:35PM 25.602 /test/meTest?id=1 200 3009ms 0cpu_ms 0kb gzip(gfe)
  03-02 08:35PM 22.637 /test/meTest?id=2 200 3008ms 0cpu_ms 0kb gzip(gfe)
  03-02 08:35PM 22.623 /test/meTest?id=3 200 3009ms 0cpu_ms 0kb gzip(gfe)
  03-02 08:35PM 22.603 /test/meTest?id=4 200 3008ms 0cpu_ms 0kb gzip(gfe)

  Once I start testing with more than 4 threads, it starts to slow down in
  its
  response time...

  So, I'd guess something would need to be clarified.. is there some
  internal
  limiting going on per ip address?  Does a long running process have a
  lower simultaneous request limit?

  On Tue, Mar 2, 2010 at 12:21 PM, Gary Orser garyor...@gmail.com wrote:
   Eli,

   You have the python request server.
   Here is the java client:
   You'll have to get the libraries yourself.

   Cheers, Gary

   import java.util.ArrayList;
   import java.util.concurrent.Callable;
   import java.util.concurrent.ExecutionException;
   import java.util.concurrent.ExecutorService;
   import java.util.concurrent.Executors;
   import java.util.concurrent.Future;

   import org.apache.commons.io.IOUtils;
   import org.apache.http.HttpHost;
   import org.apache.http.HttpResponse;
   import org.apache.http.HttpVersion;
   import org.apache.http.client.HttpClient;
   import org.apache.http.client.methods.HttpGet;
   import org.apache.http.conn.ClientConnectionManager;
   import org.apache.http.conn.params.ConnManagerParams;
   import org.apache.http.conn.params.ConnPerRouteBean;
   import org.apache.http.conn.scheme.PlainSocketFactory;
   import org.apache.http.conn.scheme.Scheme;
   import org.apache.http.conn.scheme.SchemeRegistry;
   import org.apache.http.conn.ssl.SSLSocketFactory;
   import org.apache.http.impl.client.DefaultHttpClient;
   import 

[google-appengine] Re: Error when querying the DB

[bFlood]

I'm having intermittent problems with connecting and querying, is
something wrong on GAE?

GAE Status has had the Datastore Anomaly up for a couple of hours
http://code.google.com/status/appengine



On Mar 4, 2:44 pm, Ikai L (Google) ika...@google.com wrote:
 Can you post any code? Preferably a test case that can be run.





 On Tue, Mar 2, 2010 at 5:22 PM, midi chum...@gmail.com wrote:
  I get this error when querying the DB.

  javax.jdo.JDONullIdentityException: The identity must not be null.
         at
  javax.jdo.identity.SingleFieldIdentity.assertKeyNotNull(SingleFieldIdentity 
  .java:
  97)
         at
  javax.jdo.identity.SingleFieldIdentity.setKeyAsObject(SingleFieldIdentity.j 
  ava:
  87)
         at javax.jdo.identity.StringIdentity.(StringIdentity.java:43)
         at guestbook.yttab.jdoNewObjectIdInstance(yttab.java)

  I'm able to insert records, but unable to retrieve any.

  Has anyone come across this.

  --
  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-appeng...@googlegroups.com.
  To unsubscribe from this group, send email to 
  google-appengine+unsubscr...@googlegroups.com.
  For more options, visit this group 
  athttp://groups.google.com/group/google-appengine?hl=en.

 --
 Ikai Lan
 Developer Programs Engineer, Google App 
 Enginehttp://googleappengine.blogspot.com|http://twitter.com/app_engine

-- 
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-appeng...@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.