[google-appengine] Re: Best strategy

[timh]

I have also found (in python) that startup time is much quicker if you are 
only loading core appengine modules.  Even one non core module seemed to 
heavily affect startup times (especially on M/S when gae was having a bad 
hair day ;-).  I found early on that having a fast path to cached stuff 
that didn't involve any 3rd party modules usually meant a very quick 
startup time even on the worst M/S days.  If the cache lookup failed then 
start the full stack (ad that was as lazy as possible, ie don't load CRUD 
form definitions unless the user was logged in.)

All these strategies (which could be considered over-optimisations) tended 
to make even bad days bearable on python with M/S ;-)

I have since moved to HRD which has meant I haven't had to resort to some 
of these strategies.

T

On Thursday, March 14, 2013 2:22:50 AM UTC+8, Renzo Nuccitelli wrote:
>
>  I am part of team anti "Java/GAE". There are a lot of reason because I 
> prefer Python, but the main on is the cold start problem already mentioned. 
> The fact that the cold start time more o less proportional to the number of 
> class you have in you project make Java not first citizen on GAE. Just to 
> make it clear, it is not a Java problem, is a GAE-Java interaction problem.
>
>   About it, it's not true that Python can have this problem. You can avoid 
> it with the right approach. If you could make your code to be read in a 
> lazy way, cold start would be not a problem. I just wrote a small 
> framework, Zenwarch  to do this 
> and the result is that my cold start is constant and small all the time, 
> even when the number of script files grows.
>
>  And even webapp2 has LazyHandlers (
> http://webapp-improved.appspot.com/guide/routing.html?highlight=routing%20string)
>  
> So you can avoid the cold start.
>
>  So, for small projects, use whatever language you like. But if you think 
> your app can get bigger and you want to use java, use AWS.
>
>
>
> On Tuesday, March 12, 2013 8:36:39 PM UTC-3, Carl Schroeder wrote:
>>
>> This has been documented to death on these forums with resident instances 
>> for paid apps and posted logs with missing warmup requests. 
>>
>> Also, "Routinely" is a very loose description. Does that mean that 
>> sometimes your app loads faster than 5 seconds and sometimes slower?
>> What instance size are you talking? F4s or F1?
>>
>> If you have stumbled upon something magical that accesses the user & 
>> datastore apis and never takes longer than 5 seconds to service requests in 
>> an F1, I suggest you post some code here. You would close two open issues 
>> for Google and make the people who starred them really happy.
>>
>>
>>
>> On Tuesday, March 12, 2013 11:05:21 AM UTC-7, Vinny P wrote:
>>>
>>>
>>> On Tuesday, March 12, 2013 12:18:24 PM UTC-5, Carl Schroeder wrote:

 The sentiment is not anti-Java, it is anti GAE/Java. Writing "Hello 
 world" to the datastore takes 4-5 seconds to cold start load on an F2 in 
 GAE/Java. That is on good days, it could take twice as long on stormy 
 days. 
 The more the application grows, the worse this gets.

 Why risk 5+ second response times? Wait until Google has fixed the Java 
 instance loading time issue before you embark on writing Java apps for GAE.
 FYI, I used the low-level API and no frameworks. Latency was untenable.


>>> I can't say that I share your experiences with GAE/J, I find that I can 
>>> routinely cold start instances + datastore requests in less than 5 seconds, 
>>> although I'm recently having issues with memcache slowness...
>>>
>>> True, GAE/J has problems. But so do the Python and Go runtimes. I'm 
>>> subscribed to the google-appengine-go Google group, and I see as many 
>>> complaints there, as I do on this group about Python/Java.  Giving the OP a 
>>> balanced view of the pros/cons of each runtime is the point of this thread, 
>>> and I think it's fair to let him know what he's looking at.
>>>
>>> @OP: if you're interested in looking more about Java performance, may I 
>>> recommend this thread (it's a bit of a long read, to give you fair 
>>> warning): 
>>> https://groups.google.com/d/msg/google-appengine/sA3o-PTAckc/okDqu5aE-78J
>>>  
>>>
>>

-- 
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] Conversion of google visualization charts to PDF

[Manoj Kumar]

I am trying to convert visualization charts to pdf . Are there any services 
or functions available for this conversion ?

-- 
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: instances dying is a permanent states for datastore apps?

[stevep]

I am uncertain about GAE given recent history, but have hope. Certainly 
given MS is deprecated, we cannot hold G. accountable for issues there. 
They **clearly** recommend HR, so MS app are 100% caveat emptor. However, 
the SO and Google Groups threads recently have been consumed with ire not 
limited to MS. A while ago, Jeff S. (whose posts I value the most along 
with Drake) posited that G. would have fixed the issues had they been able 
to do so. Going way back (when I started with GAE) billing was based on CPU 
milliseconds consumed. My guess is they thought this was highly disruptive. 
Then after beta, we got billed for 15 minute instance slices which was a 
big change from beta. This suggest that the initial assumptions were wrong 
(sh*t happens sometimes even if you are the brightest bulb in the pack). 
Overall, I think Jeff is right. There are some problems that can not be 
fixed given GAE's initial architecture. However, there may be some big 
changes coming with the App>Server architecture that only trusted devs (me 
excluded) get to enjoy. As I read the limited docs about what this entails, 
I wonder if this will be a fundamental change for GAE. It appears to fix 
most of my complaints, so I will be happy.

-- 
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: Is GAE the right choice for e-commerce?

[Adam Wooding]

Hi Mike and Kaan,

Thank you very much for your replies.

Mike congratulations on the success of shoesofprey - I have been very 
interested in your story as what you have achieved and the direction you 
are heading in is similar to what we are trying to achieve with our do it 
yourself wardrobe products and our wardrobe designer. Thank you for the 
inspiration!

I have come from a PHP background, but since finding out about Google App 
Engine I am now planning on switching to Python as it just seems like such 
a solid and reliable infrastructure. The scaling is also a big bonus.

Thanks again for taking the time to reply to me, it is very much 
appreciated :)

Cheers,
Adam


On Thursday, March 14, 2013 10:08:32 AM UTC+10, Mike wrote:
>
> Hi Adam and Kaan
>
> Yes, we still use AppEngine for our website, which is written in Python. 
> Our 3D shoe designer infrastructure though is hosted elsewhere for now.
>
> We're big fans of AppEngine!! It's great not having to think about 
> infrastructure, and having rich APIs already installed. (Disclosure: I'm a 
> former goog software engineer, so quite biased!) :-)
>
> Not only is the platform a pleasure to use, but it's scaled beautifully 
> when we've needed it to, for example the time when a 16 year old video 
> blogger sent 1/2 million people to our site: 
> http://www.22michaels.com/2010/03/juicystar07-and-world-of-new-media.html
>
> Kaan - that's interesting it was slow! Where are you based? How slow was 
> it? We're also using Google's PageSpeed service, so it shouldn't be slow.
>
> Cheers
> Mike
>
>
>
> On Thursday, March 14, 2013 8:38:15 AM UTC+11, Kaan Soral wrote:
>>
>> You can check the headers with something like Firebug yourself, the 
>> answer is 99% Yes, as server seems to be Google Frontend
>>
>> Also even before seeing the headers, I was 90% sure it was still an 
>> Appengine app, because it took a significant amount of time to load the app 
>> initially, might not have been Appengine's fault tho
>>
>> On Wednesday, March 13, 2013 1:11:22 AM UTC+2, Adam Wooding wrote:
>>>
>>> Hi Mike,
>>>
>>> I just came across your post and had a look at your Shoes of Prey app - 
>>> it is fantastic!
>>>
>>> I am also about to begin work creating a similar app, but for custom 
>>> made wardrobes / closets. I'm just wondering - which language did you build 
>>> your app on? Are you still running it on Google App Engine?
>>>
>>> Any tips / advice you could give would be much appreciated.
>>>
>>> Thank you very much,
>>> Adam Wooding
>>>
>>>
>>> On Monday, 1 February 2010 23:19:04 UTC+10, Mike wrote:

 Hi NG

 We are running our business on AppEngine. (Search "Shoes of Prey" on
 Google to find us.)

 So far, it is going really well. AppEngine is a delight to develop on,
 and you can't argue with the cost. (I've only been charged $0.01 so
 far. Although, as I've posted in another thread, the small charge by
 itself was problematic for me.) :)

 I had to write the entire ecommerce platform from scratch - which
 suited me given the very custom nature of our business - however you
 may not be as keen as me. It really depends on your business.

 We choose AppEngine primarily because a) 2 of us used to work at
 Google, and we love AppEngine b) if we start serving a lot of traffic/
 bandwidth we want something scalable. As I said earlier as well, the
 API is really nice and makes developing a breeze.

 The only thing I wish AppEngine had was HTTPS support for custom
 domains, and I'm hopeful that one day it will be supported. There are
 workarounds too. Once AppEngine has HTTPS support and a few open-
 source ecommerce software packages, it will be a really great platform
 I would think.

 Good luck.

 Mike

 On Jan 31, 4:31 pm, decuman  wrote:
 > Hello,
 >
 > At the moment I'm thinking of building a small/medium online selling
 > business and before investing more of my time (and money) into GAE
 > based development it would be just great to know some experienced
 > users and expert thoughts and opinions on it.
 >
 > As far as I can see (after reading related books, articles and message
 > group threads) GAE is just a perfect solution for prototyping and
 > building a social networking applications (Blogs, Chats, Galleries,
 > Message boards etc.) which requires tracking a lot of users and
 > storing data... which is great. But there is quite a few (literally
 > none) of nice business/e-commerce applications with decent product
 > galleries, shopping carts and checkout functionality and payment
 > service integration. Also there are lots of complains and negative
 > responses pointing to big GAE functional limitations (which are not
 > going to improve soon or ever) and overall practicability of using it
 > as a reliable e-commerce platform. In particular (PayPal, Google
 > Che

[google-appengine] Re: Is GAE the right choice for e-commerce?

[Kaan Soral]

Wow that youtube story is really interesting and inspiring, thanks for 
sharing.

I also share your feelings towards AppEngine. I've been using AppEngine for 
~2 years now, life is better.

I'm from Turkey, the Net graph of Firebug showed 350ms when I first 
checked, but the initial load was really slow, might be a DNS or third 
party library issue, also might be an issue with my network, currently 
checked the website again, loaded very fast, extremely fast. (also tested a 
shift-refresh, it was fast again, however optimizely gave 400 bad request 
and delayed the page load by 700ms, unimportant). So to sum up, don't 
worry, it was probably an isolated network issue


On Thursday, March 14, 2013 2:08:32 AM UTC+2, Mike wrote:
>
> Hi Adam and Kaan
>
> Yes, we still use AppEngine for our website, which is written in Python. 
> Our 3D shoe designer infrastructure though is hosted elsewhere for now.
>
> We're big fans of AppEngine!! It's great not having to think about 
> infrastructure, and having rich APIs already installed. (Disclosure: I'm a 
> former goog software engineer, so quite biased!) :-)
>
> Not only is the platform a pleasure to use, but it's scaled beautifully 
> when we've needed it to, for example the time when a 16 year old video 
> blogger sent 1/2 million people to our site: 
> http://www.22michaels.com/2010/03/juicystar07-and-world-of-new-media.html
>
> Kaan - that's interesting it was slow! Where are you based? How slow was 
> it? We're also using Google's PageSpeed service, so it shouldn't be slow.
>
> Cheers
> Mike
>
>
>
> On Thursday, March 14, 2013 8:38:15 AM UTC+11, Kaan Soral wrote:
>>
>> You can check the headers with something like Firebug yourself, the 
>> answer is 99% Yes, as server seems to be Google Frontend
>>
>> Also even before seeing the headers, I was 90% sure it was still an 
>> Appengine app, because it took a significant amount of time to load the app 
>> initially, might not have been Appengine's fault tho
>>
>> On Wednesday, March 13, 2013 1:11:22 AM UTC+2, Adam Wooding wrote:
>>>
>>> Hi Mike,
>>>
>>> I just came across your post and had a look at your Shoes of Prey app - 
>>> it is fantastic!
>>>
>>> I am also about to begin work creating a similar app, but for custom 
>>> made wardrobes / closets. I'm just wondering - which language did you build 
>>> your app on? Are you still running it on Google App Engine?
>>>
>>> Any tips / advice you could give would be much appreciated.
>>>
>>> Thank you very much,
>>> Adam Wooding
>>>
>>>
>>> On Monday, 1 February 2010 23:19:04 UTC+10, Mike wrote:

 Hi NG

 We are running our business on AppEngine. (Search "Shoes of Prey" on
 Google to find us.)

 So far, it is going really well. AppEngine is a delight to develop on,
 and you can't argue with the cost. (I've only been charged $0.01 so
 far. Although, as I've posted in another thread, the small charge by
 itself was problematic for me.) :)

 I had to write the entire ecommerce platform from scratch - which
 suited me given the very custom nature of our business - however you
 may not be as keen as me. It really depends on your business.

 We choose AppEngine primarily because a) 2 of us used to work at
 Google, and we love AppEngine b) if we start serving a lot of traffic/
 bandwidth we want something scalable. As I said earlier as well, the
 API is really nice and makes developing a breeze.

 The only thing I wish AppEngine had was HTTPS support for custom
 domains, and I'm hopeful that one day it will be supported. There are
 workarounds too. Once AppEngine has HTTPS support and a few open-
 source ecommerce software packages, it will be a really great platform
 I would think.

 Good luck.

 Mike

 On Jan 31, 4:31 pm, decuman  wrote:
 > Hello,
 >
 > At the moment I'm thinking of building a small/medium online selling
 > business and before investing more of my time (and money) into GAE
 > based development it would be just great to know some experienced
 > users and expert thoughts and opinions on it.
 >
 > As far as I can see (after reading related books, articles and message
 > group threads) GAE is just a perfect solution for prototyping and
 > building a social networking applications (Blogs, Chats, Galleries,
 > Message boards etc.) which requires tracking a lot of users and
 > storing data... which is great. But there is quite a few (literally
 > none) of nice business/e-commerce applications with decent product
 > galleries, shopping carts and checkout functionality and payment
 > service integration. Also there are lots of complains and negative
 > responses pointing to big GAE functional limitations (which are not
 > going to improve soon or ever) and overall practicability of using it
 > as a reliable e-commerce platform. In particular (PayPal, Google
 > Checkout int

[google-appengine] Re: Is GAE the right choice for e-commerce?

[Mike]

Hi Adam and Kaan

Yes, we still use AppEngine for our website, which is written in Python. 
Our 3D shoe designer infrastructure though is hosted elsewhere for now.

We're big fans of AppEngine!! It's great not having to think about 
infrastructure, and having rich APIs already installed. (Disclosure: I'm a 
former goog software engineer, so quite biased!) :-)

Not only is the platform a pleasure to use, but it's scaled beautifully 
when we've needed it to, for example the time when a 16 year old video 
blogger sent 1/2 million people to our 
site: http://www.22michaels.com/2010/03/juicystar07-and-world-of-new-media.html

Kaan - that's interesting it was slow! Where are you based? How slow was 
it? We're also using Google's PageSpeed service, so it shouldn't be slow.

Cheers
Mike



On Thursday, March 14, 2013 8:38:15 AM UTC+11, Kaan Soral wrote:
>
> You can check the headers with something like Firebug yourself, the answer 
> is 99% Yes, as server seems to be Google Frontend
>
> Also even before seeing the headers, I was 90% sure it was still an 
> Appengine app, because it took a significant amount of time to load the app 
> initially, might not have been Appengine's fault tho
>
> On Wednesday, March 13, 2013 1:11:22 AM UTC+2, Adam Wooding wrote:
>>
>> Hi Mike,
>>
>> I just came across your post and had a look at your Shoes of Prey app - 
>> it is fantastic!
>>
>> I am also about to begin work creating a similar app, but for custom made 
>> wardrobes / closets. I'm just wondering - which language did you build your 
>> app on? Are you still running it on Google App Engine?
>>
>> Any tips / advice you could give would be much appreciated.
>>
>> Thank you very much,
>> Adam Wooding
>>
>>
>> On Monday, 1 February 2010 23:19:04 UTC+10, Mike wrote:
>>>
>>> Hi NG
>>>
>>> We are running our business on AppEngine. (Search "Shoes of Prey" on
>>> Google to find us.)
>>>
>>> So far, it is going really well. AppEngine is a delight to develop on,
>>> and you can't argue with the cost. (I've only been charged $0.01 so
>>> far. Although, as I've posted in another thread, the small charge by
>>> itself was problematic for me.) :)
>>>
>>> I had to write the entire ecommerce platform from scratch - which
>>> suited me given the very custom nature of our business - however you
>>> may not be as keen as me. It really depends on your business.
>>>
>>> We choose AppEngine primarily because a) 2 of us used to work at
>>> Google, and we love AppEngine b) if we start serving a lot of traffic/
>>> bandwidth we want something scalable. As I said earlier as well, the
>>> API is really nice and makes developing a breeze.
>>>
>>> The only thing I wish AppEngine had was HTTPS support for custom
>>> domains, and I'm hopeful that one day it will be supported. There are
>>> workarounds too. Once AppEngine has HTTPS support and a few open-
>>> source ecommerce software packages, it will be a really great platform
>>> I would think.
>>>
>>> Good luck.
>>>
>>> Mike
>>>
>>> On Jan 31, 4:31 pm, decuman  wrote:
>>> > Hello,
>>> >
>>> > At the moment I'm thinking of building a small/medium online selling
>>> > business and before investing more of my time (and money) into GAE
>>> > based development it would be just great to know some experienced
>>> > users and expert thoughts and opinions on it.
>>> >
>>> > As far as I can see (after reading related books, articles and message
>>> > group threads) GAE is just a perfect solution for prototyping and
>>> > building a social networking applications (Blogs, Chats, Galleries,
>>> > Message boards etc.) which requires tracking a lot of users and
>>> > storing data... which is great. But there is quite a few (literally
>>> > none) of nice business/e-commerce applications with decent product
>>> > galleries, shopping carts and checkout functionality and payment
>>> > service integration. Also there are lots of complains and negative
>>> > responses pointing to big GAE functional limitations (which are not
>>> > going to improve soon or ever) and overall practicability of using it
>>> > as a reliable e-commerce platform. In particular (PayPal, Google
>>> > Checkout integration)
>>> >
>>> > It wasn't a very deep and thoughtful investigation but the outlined
>>> > above is just my personal subjective feeling so far. I would really
>>> > love to know the opinion and thoughts on this matter from GAE experts.
>>> > Shell I move forward with Google App Engine development or it would be
>>> > move wise to consider some other solution?
>>> >
>>> > Thanks in advance!
>>> > NG
>>>
>>>

-- 
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/g

[google-appengine] send entity ID to javascript from jsp. Have Java script request data from servlet and display in jsp

[Aidan Mack]

Hi,

Im trying to create a system so that I can get data from servlet without 
redirecting to a new jsp.

Im trying to do this using javascript.

Currently Im stuck trying to send a entity key to javascript. Can I do that?

I will then have javascript send that key on to a servlet and display the 
returned data with in the current jsp.

Thanks
Aidan

-- 
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: Is GAE the right choice for e-commerce?

[Kaan Soral]

You can check the headers with something like Firebug yourself, the answer 
is 99% Yes, as server seems to be Google Frontend

Also even before seeing the headers, I was 90% sure it was still an 
Appengine app, because it took a significant amount of time to load the app 
initially, might not have been Appengine's fault tho

On Wednesday, March 13, 2013 1:11:22 AM UTC+2, Adam Wooding wrote:
>
> Hi Mike,
>
> I just came across your post and had a look at your Shoes of Prey app - it 
> is fantastic!
>
> I am also about to begin work creating a similar app, but for custom made 
> wardrobes / closets. I'm just wondering - which language did you build your 
> app on? Are you still running it on Google App Engine?
>
> Any tips / advice you could give would be much appreciated.
>
> Thank you very much,
> Adam Wooding
>
>
> On Monday, 1 February 2010 23:19:04 UTC+10, Mike wrote:
>>
>> Hi NG
>>
>> We are running our business on AppEngine. (Search "Shoes of Prey" on
>> Google to find us.)
>>
>> So far, it is going really well. AppEngine is a delight to develop on,
>> and you can't argue with the cost. (I've only been charged $0.01 so
>> far. Although, as I've posted in another thread, the small charge by
>> itself was problematic for me.) :)
>>
>> I had to write the entire ecommerce platform from scratch - which
>> suited me given the very custom nature of our business - however you
>> may not be as keen as me. It really depends on your business.
>>
>> We choose AppEngine primarily because a) 2 of us used to work at
>> Google, and we love AppEngine b) if we start serving a lot of traffic/
>> bandwidth we want something scalable. As I said earlier as well, the
>> API is really nice and makes developing a breeze.
>>
>> The only thing I wish AppEngine had was HTTPS support for custom
>> domains, and I'm hopeful that one day it will be supported. There are
>> workarounds too. Once AppEngine has HTTPS support and a few open-
>> source ecommerce software packages, it will be a really great platform
>> I would think.
>>
>> Good luck.
>>
>> Mike
>>
>> On Jan 31, 4:31 pm, decuman  wrote:
>> > Hello,
>> >
>> > At the moment I'm thinking of building a small/medium online selling
>> > business and before investing more of my time (and money) into GAE
>> > based development it would be just great to know some experienced
>> > users and expert thoughts and opinions on it.
>> >
>> > As far as I can see (after reading related books, articles and message
>> > group threads) GAE is just a perfect solution for prototyping and
>> > building a social networking applications (Blogs, Chats, Galleries,
>> > Message boards etc.) which requires tracking a lot of users and
>> > storing data... which is great. But there is quite a few (literally
>> > none) of nice business/e-commerce applications with decent product
>> > galleries, shopping carts and checkout functionality and payment
>> > service integration. Also there are lots of complains and negative
>> > responses pointing to big GAE functional limitations (which are not
>> > going to improve soon or ever) and overall practicability of using it
>> > as a reliable e-commerce platform. In particular (PayPal, Google
>> > Checkout integration)
>> >
>> > It wasn't a very deep and thoughtful investigation but the outlined
>> > above is just my personal subjective feeling so far. I would really
>> > love to know the opinion and thoughts on this matter from GAE experts.
>> > Shell I move forward with Google App Engine development or it would be
>> > move wise to consider some other solution?
>> >
>> > Thanks in advance!
>> > NG
>>
>>

-- 
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] Re: Best strategy

[Victor Trot]

Thank you so much for the links and ideas Renzo. I did not expect this
thread to become a Java vs Python war :P


On Wed, Mar 13, 2013 at 11:22 AM, Renzo Nuccitelli  wrote:

>  I am part of team anti "Java/GAE". There are a lot of reason because I
> prefer Python, but the main on is the cold start problem already mentioned.
> The fact that the cold start time more o less proportional to the number of
> class you have in you project make Java not first citizen on GAE. Just to
> make it clear, it is not a Java problem, is a GAE-Java interaction problem.
>
>   About it, it's not true that Python can have this problem. You can avoid
> it with the right approach. If you could make your code to be read in a
> lazy way, cold start would be not a problem. I just wrote a small
> framework, Zenwarch  to do this
> and the result is that my cold start is constant and small all the time,
> even when the number of script files grows.
>
>  And even webapp2 has LazyHandlers (
> http://webapp-improved.appspot.com/guide/routing.html?highlight=routing%20string)
> So you can avoid the cold start.
>
>  So, for small projects, use whatever language you like. But if you think
> your app can get bigger and you want to use java, use AWS.
>
>
>
> On Tuesday, March 12, 2013 8:36:39 PM UTC-3, Carl Schroeder wrote:
>>
>> This has been documented to death on these forums with resident instances
>> for paid apps and posted logs with missing warmup requests.
>>
>> Also, "Routinely" is a very loose description. Does that mean that
>> sometimes your app loads faster than 5 seconds and sometimes slower?
>> What instance size are you talking? F4s or F1?
>>
>> If you have stumbled upon something magical that accesses the user &
>> datastore apis and never takes longer than 5 seconds to service requests in
>> an F1, I suggest you post some code here. You would close two open issues
>> for Google and make the people who starred them really happy.
>>
>>
>>
>> On Tuesday, March 12, 2013 11:05:21 AM UTC-7, Vinny P wrote:
>>>
>>>
>>> On Tuesday, March 12, 2013 12:18:24 PM UTC-5, Carl Schroeder wrote:

 The sentiment is not anti-Java, it is anti GAE/Java. Writing "Hello
 world" to the datastore takes 4-5 seconds to cold start load on an F2 in
 GAE/Java. That is on good days, it could take twice as long on stormy days.
 The more the application grows, the worse this gets.

 Why risk 5+ second response times? Wait until Google has fixed the Java
 instance loading time issue before you embark on writing Java apps for GAE.
 FYI, I used the low-level API and no frameworks. Latency was untenable.


>>> I can't say that I share your experiences with GAE/J, I find that I can
>>> routinely cold start instances + datastore requests in less than 5 seconds,
>>> although I'm recently having issues with memcache slowness...
>>>
>>> True, GAE/J has problems. But so do the Python and Go runtimes. I'm
>>> subscribed to the google-appengine-go Google group, and I see as many
>>> complaints there, as I do on this group about Python/Java.  Giving the OP a
>>> balanced view of the pros/cons of each runtime is the point of this thread,
>>> and I think it's fair to let him know what he's looking at.
>>>
>>> @OP: if you're interested in looking more about Java performance, may I
>>> recommend this thread (it's a bit of a long read, to give you fair
>>> warning): https://groups.**google.com/d/msg/google-**
>>> appengine/sA3o-PTAckc/**okDqu5aE-78J
>>>
>>>
>>  --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/NjF11Uy-4EM/unsubscribe?hl=en
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Re: [google-appengine] Re: instances dying is a permanent states for datastore apps?

[Barry Hunter]

 I believe it would be less work to move out of appengine rather than
> moving to HDR.
>

You will have to do one or the other soon anyway. M/S will be turned off.

-- 
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] Re: instances dying is a permanent states for datastore apps?

[Rafael]

This is my biggest concern. I don't care about technical problems, I care
about shipping high quality products. That was the reason why we picked
appengine 2 years ago.

The problem is that the service isn't working well and we can't predict for
how long. We need to have any insight on how long this instability will
last, so we can play ahead.

We have serialized blobs everywhere across our application. We're paying
the price for "clever optimizations". I believe it would be less work to
move out of appengine rather than moving to HDR.


On Wed, Mar 13, 2013 at 10:27 AM, johnP  wrote:

> That's you projecting your hopes, that someone is calmly fixing the
> problem.
>
> But one of the attributes of competent leadership is effective
> communication.  When customers see that effective communication is lacking,
> they a symptom of poor leadership. If appengine has poor leadership, this
> is an existential threat to everyone who has bet their future on this
> platform.
>
>
>
> On Wednesday, March 13, 2013 10:13:03 AM UTC-7, barryhunter wrote:
>
>> I didnt say there where not problems with HRD.
>>
>> Just that its expected there will be problems with M/S. Google have
>> pretty much said they WONT even try to be fixing them.
>>
>> Any resources Google have working on the issue, will be fixing it
>> (ultimately) within the HRD codebase. They probably wont back-port it to
>> M/S. M/S is like a live grenade just waiting to explode, they wont touch
>> it.
>>
>>
>> Alas its just in Googles culture to be tight-lipped about upcoming
>> changes (and that includes bug fixes) - so as you say we are just all
>> running around like headless chickens, while Google hopefully has
>> someone calmly sitting there working on the issue (we just dont know about
>> it). One day just to push it into production with little fanfare.
>>
>> Google's timescale on fixing issues, is also almost certainly orders of
>> magnitude slower than most people would like.
>>
>>
>>
>>  On Wed, Mar 13, 2013 at 4:17 PM, johnP  wrote:
>>
>>>
>>> Barry -
>>>
>>> If you look through this message board and at the issue tracker, you'll
>>> see that many people with HRD are also affected by this issue.
>>>
>>> As often is the case, the big problem is not the crime - it's the
>>> cover-up.  Everyone here can understand technical issues, if people are
>>> working to fix them.  The non-response from Google is what's freaking
>>> people out.
>>>
>>>
>>>
>>>
>>> On Wednesday, March 13, 2013 8:31:07 AM UTC-7, barryhunter wrote:
>>>



 On Wed, Mar 13, 2013 at 9:36 AM, Rafael  wrote:

> YES! I'm on the master/slave.
>
> Google putting a message at the top of the appengine site saying that
> it's deprecated isn't an excuse for extreme reduction of performance.
>

 The depreciation pretty much is Google admitting the can't (and/or
 won't) fix M/S. They KNOW it's bad, and want you to stop using it.

 M/S is a sinking ship. Google arent allocating much resources to
 bailing it out. They've moved on to brighter and better things.



> Migrating to HDR will never happen to me.
>

 Then you have pretty much resigned yourself to issues. Why are you
 pointing a loaded gun at your own foot?


  By continuing to use M/S you making yourself and Google look bad.

>>>  --
>>> 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?hl=en
>>> .
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out
>>> .
>>>
>>>
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

[google-appengine] Re: Best strategy

[Renzo Nuccitelli]

 I am part of team anti "Java/GAE". There are a lot of reason because I 
prefer Python, but the main on is the cold start problem already mentioned. 
The fact that the cold start time more o less proportional to the number of 
class you have in you project make Java not first citizen on GAE. Just to 
make it clear, it is not a Java problem, is a GAE-Java interaction problem.

  About it, it's not true that Python can have this problem. You can avoid 
it with the right approach. If you could make your code to be read in a 
lazy way, cold start would be not a problem. I just wrote a small 
framework, Zenwarch  to do this and 
the result is that my cold start is constant and small all the time, even 
when the number of script files grows.

 And even webapp2 has LazyHandlers (
http://webapp-improved.appspot.com/guide/routing.html?highlight=routing%20string)
 
So you can avoid the cold start.

 So, for small projects, use whatever language you like. But if you think 
your app can get bigger and you want to use java, use AWS.



On Tuesday, March 12, 2013 8:36:39 PM UTC-3, Carl Schroeder wrote:
>
> This has been documented to death on these forums with resident instances 
> for paid apps and posted logs with missing warmup requests. 
>
> Also, "Routinely" is a very loose description. Does that mean that 
> sometimes your app loads faster than 5 seconds and sometimes slower?
> What instance size are you talking? F4s or F1?
>
> If you have stumbled upon something magical that accesses the user & 
> datastore apis and never takes longer than 5 seconds to service requests in 
> an F1, I suggest you post some code here. You would close two open issues 
> for Google and make the people who starred them really happy.
>
>
>
> On Tuesday, March 12, 2013 11:05:21 AM UTC-7, Vinny P wrote:
>>
>>
>> On Tuesday, March 12, 2013 12:18:24 PM UTC-5, Carl Schroeder wrote:
>>>
>>> The sentiment is not anti-Java, it is anti GAE/Java. Writing "Hello 
>>> world" to the datastore takes 4-5 seconds to cold start load on an F2 in 
>>> GAE/Java. That is on good days, it could take twice as long on stormy days. 
>>> The more the application grows, the worse this gets.
>>>
>>> Why risk 5+ second response times? Wait until Google has fixed the Java 
>>> instance loading time issue before you embark on writing Java apps for GAE.
>>> FYI, I used the low-level API and no frameworks. Latency was untenable.
>>>
>>>
>> I can't say that I share your experiences with GAE/J, I find that I can 
>> routinely cold start instances + datastore requests in less than 5 seconds, 
>> although I'm recently having issues with memcache slowness...
>>
>> True, GAE/J has problems. But so do the Python and Go runtimes. I'm 
>> subscribed to the google-appengine-go Google group, and I see as many 
>> complaints there, as I do on this group about Python/Java.  Giving the OP a 
>> balanced view of the pros/cons of each runtime is the point of this thread, 
>> and I think it's fair to let him know what he's looking at.
>>
>> @OP: if you're interested in looking more about Java performance, may I 
>> recommend this thread (it's a bit of a long read, to give you fair 
>> warning): 
>> https://groups.google.com/d/msg/google-appengine/sA3o-PTAckc/okDqu5aE-78J
>>  
>>
>

-- 
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] Appspot owner

[Barry Hunter]

There is no offical way.

You can try emailing [appid]@gmail.com - as they might of setup the app to
match their Gmail identity. (would of have to been setup that way, the
gmail account setup before appengine)

If they might be abusing the AppEngine TOS, there is
https://support.google.com/code/bin/request.py?contact_type=AppEngineAbuse
or if Copyright is involved
http://www.google.com/dmca.html




On Wed, Mar 13, 2013 at 10:20 AM, Károly Huber wrote:

> How can I find out who owns/controlls a particular appspot address/ID?  My
> organization's info is misrepresented on the said site, and have no way of
> contact.
>
> --
> 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.
>
>
>

-- 
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: 1.7.6 Pre-release SDKs Available

[stevep]

Janani wrote about the new GAE release: "Task Queue tasks may now be added 
and deleted asynchronously. This allows applications to perform common task 
queue operations without blocking. This is an experimental feature."

And just yesterday I started a thread complaining about the extreme 
variability of TQ additions API**. I will be on this like white on rice. 
Thanks G.

**recent log shows 1057 ms latency comprised of 0-cpu and 1057 api which 
was immediately preceded (within 2 seconds) by 0/47ms for the exact same 
handler function:-)

-- 
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] How to know if app version is DEFAULT version?

[Takashi Matsuo]

Hi Moises,

You can use os.environ['HTTP_HOST'] for comparison as long as the hostname
doesn't contain the 'version' subdomain part. Are you using hostname with
the 'version.app-id.appspot.com' style, or you're just using '
app-id.appspot.com'?



On Wed, Mar 13, 2013 at 3:13 AM, Moises Belchin wrote:

> Hi guys,
>
> Is there any way to know if a version of my app is the DEFAULT version?
>
> I saw os.environ['DEFAULT_VERSION_HOSTNAME'] and
> os.environ['CURRENT_VERSION_ID'] but I didn't find any way to compare two
> of them and determine if this current version y the default version.
>
> Thanks for help.
>
> Regards.
> Moisés Belchín.
>
> --
> 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.
>
>
>



-- 
Takashi Matsuo | Developers Advocate | tmat...@google.com

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

[google-appengine] Re: Is GAE the right choice for e-commerce?

[Adam Wooding]

Hi Mike,

I just came across your post and had a look at your Shoes of Prey app - it 
is fantastic!

I am also about to begin work creating a similar app, but for custom made 
wardrobes / closets. I'm just wondering - which language did you build your 
app on? Are you still running it on Google App Engine?

Any tips / advice you could give would be much appreciated.

Thank you very much,
Adam Wooding


On Monday, 1 February 2010 23:19:04 UTC+10, Mike wrote:
>
> Hi NG
>
> We are running our business on AppEngine. (Search "Shoes of Prey" on
> Google to find us.)
>
> So far, it is going really well. AppEngine is a delight to develop on,
> and you can't argue with the cost. (I've only been charged $0.01 so
> far. Although, as I've posted in another thread, the small charge by
> itself was problematic for me.) :)
>
> I had to write the entire ecommerce platform from scratch - which
> suited me given the very custom nature of our business - however you
> may not be as keen as me. It really depends on your business.
>
> We choose AppEngine primarily because a) 2 of us used to work at
> Google, and we love AppEngine b) if we start serving a lot of traffic/
> bandwidth we want something scalable. As I said earlier as well, the
> API is really nice and makes developing a breeze.
>
> The only thing I wish AppEngine had was HTTPS support for custom
> domains, and I'm hopeful that one day it will be supported. There are
> workarounds too. Once AppEngine has HTTPS support and a few open-
> source ecommerce software packages, it will be a really great platform
> I would think.
>
> Good luck.
>
> Mike
>
> On Jan 31, 4:31 pm, decuman  wrote:
> > Hello,
> >
> > At the moment I'm thinking of building a small/medium online selling
> > business and before investing more of my time (and money) into GAE
> > based development it would be just great to know some experienced
> > users and expert thoughts and opinions on it.
> >
> > As far as I can see (after reading related books, articles and message
> > group threads) GAE is just a perfect solution for prototyping and
> > building a social networking applications (Blogs, Chats, Galleries,
> > Message boards etc.) which requires tracking a lot of users and
> > storing data... which is great. But there is quite a few (literally
> > none) of nice business/e-commerce applications with decent product
> > galleries, shopping carts and checkout functionality and payment
> > service integration. Also there are lots of complains and negative
> > responses pointing to big GAE functional limitations (which are not
> > going to improve soon or ever) and overall practicability of using it
> > as a reliable e-commerce platform. In particular (PayPal, Google
> > Checkout integration)
> >
> > It wasn't a very deep and thoughtful investigation but the outlined
> > above is just my personal subjective feeling so far. I would really
> > love to know the opinion and thoughts on this matter from GAE experts.
> > Shell I move forward with Google App Engine development or it would be
> > move wise to consider some other solution?
> >
> > Thanks in advance!
> > NG
>
>

-- 
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: Cloud SQL & Blobstore Simultaneously -- good way to handle Django image uploads?

[Chris]

Hi KScott,

Do you have one example of upload images resize these and save in cloud 
sql? thank you very much

El domingo, 26 de agosto de 2012 04:10:32 UTC+2, seafangs escribió:
>
> Hello,
>
> I'm new to GAE (and this forum), please forgive any ignorance on my part. 
> I've been searching around to find out what the best practice is, to allow 
> users to upload images using Django on GAE. The clincher is that I want to 
> use Cloud SQL.
>
> I see that the docs recommend the Blobstore as the place to store images. 
> I understand that I am also able to store images in a Cloud SQL MEDIUMBLOB 
> (or equivalent) field (or even in a TextField in a binary form). However I 
> also understand that the latter approaches -- storing it into a MEDIUMBLOB 
> or as binary data -- are advised against.
>
> So that brings me back to storing it in the Blobstore. But will I be able 
> to use the Blobstore and Cloud SQL in the same GAE environment? I got the 
> impression that the Datastore and Cloud SQL were more or less alternatives 
> to each other. But I also get the impression that Blobstore is separate, in 
> some sense, from the normal Datastore.
>
> Can anyone offer me any guidance on a best approach?
>
>

-- 
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] Re: Error code 202

[robert . cooper]

We are seeing this of flashpanel-staging. It would be really great if you 
could just let us know what we can do to mitigate this.

On Friday, March 9, 2012 12:09:14 PM UTC-5, Takashi Matsuo (Google) wrote:
>
> Sorry to chiming in a bit late here.
> If anyone is still suffering from (Error code 202), please let me know
> your app-ids and the time of the occurrence.
>
> I'll try my best to solve the issue.
>
> -- Takashi
>
> On Sat, Mar 10, 2012 at 12:25 AM, Ronoaldo José de Lana Pereira
> > wrote:
> > Same here, my apps is Java, concurrent requests enabled, on MS (sadly 
> ...)
> >
> > Em sexta-feira, 9 de março de 2012 08h27min15s UTC-3, Nikolai escreveu:
> >>
> >> +1
> >> same here
> >>
> >> Am Mittwoch, 7. März 2012 10:19:15 UTC+1 schrieb tarun2000:
> >>>
> >>>
> >>> I keep getting:  A problem was encountered with the process that 
> handled
> >>> this request, causing it to exit. This is likely to cause a new 
> process to
> >>> be used for the next request to your application. (Error code 202)
> >>>
> >>> It seems like the issue happens right after uploading a new version or 
> on
> >>> cold start.  It seems to disappear after a while.  The rpcs that fail 
> may be
> >>> returning a lot of data.  Any idea what's wrong?
> >
> > --
> > 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/-/vCTQyKvK20gJ.
> >
> > To post to this group, send email to 
> > google-a...@googlegroups.com
> .
> > To unsubscribe from this group, send email to
> > google-appengi...@googlegroups.com .
> > For more options, visit this group at
> > http://groups.google.com/group/google-appengine?hl=en.
>
> -- 
> Takashi Matsuo | Developer Advocate | tma...@google.com 
>  | 03-6384-9224
>
>

-- 
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] Appspot owner

[Károly Huber]

How can I find out who owns/controlls a particular appspot address/ID?  My 
organization's info is misrepresented on the said site, and have no way of 
contact.  

-- 
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] Re: Error code 202

[robert . cooper]

Err... flashpanel-staging and a recent one is 2013-03-12 22:48:34.425
On Friday, March 9, 2012 12:09:14 PM UTC-5, Takashi Matsuo (Google) wrote:
>
> Sorry to chiming in a bit late here.
> If anyone is still suffering from (Error code 202), please let me know
> your app-ids and the time of the occurrence.
>
> I'll try my best to solve the issue.
>
> -- Takashi
>
> On Sat, Mar 10, 2012 at 12:25 AM, Ronoaldo José de Lana Pereira
> > wrote:
> > Same here, my apps is Java, concurrent requests enabled, on MS (sadly 
> ...)
> >
> > Em sexta-feira, 9 de março de 2012 08h27min15s UTC-3, Nikolai escreveu:
> >>
> >> +1
> >> same here
> >>
> >> Am Mittwoch, 7. März 2012 10:19:15 UTC+1 schrieb tarun2000:
> >>>
> >>>
> >>> I keep getting:  A problem was encountered with the process that 
> handled
> >>> this request, causing it to exit. This is likely to cause a new 
> process to
> >>> be used for the next request to your application. (Error code 202)
> >>>
> >>> It seems like the issue happens right after uploading a new version or 
> on
> >>> cold start.  It seems to disappear after a while.  The rpcs that fail 
> may be
> >>> returning a lot of data.  Any idea what's wrong?
> >
> > --
> > 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/-/vCTQyKvK20gJ.
> >
> > To post to this group, send email to 
> > google-a...@googlegroups.com
> .
> > To unsubscribe from this group, send email to
> > google-appengi...@googlegroups.com .
> > For more options, visit this group at
> > http://groups.google.com/group/google-appengine?hl=en.
>
> -- 
> Takashi Matsuo | Developer Advocate | tma...@google.com 
>  | 03-6384-9224
>
>

-- 
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] Re: instances dying is a permanent states for datastore apps?

[johnP]

That's you projecting your hopes, that someone is calmly fixing the 
problem.  

But one of the attributes of competent leadership is effective 
communication.  When customers see that effective communication is lacking, 
they a symptom of poor leadership. If appengine has poor leadership, this 
is an existential threat to everyone who has bet their future on this 
platform.



On Wednesday, March 13, 2013 10:13:03 AM UTC-7, barryhunter wrote:
>
> I didnt say there where not problems with HRD. 
>
> Just that its expected there will be problems with M/S. Google have pretty 
> much said they WONT even try to be fixing them. 
>
> Any resources Google have working on the issue, will be fixing it 
> (ultimately) within the HRD codebase. They probably wont back-port it to 
> M/S. M/S is like a live grenade just waiting to explode, they wont touch 
> it. 
>
>
> Alas its just in Googles culture to be tight-lipped about upcoming changes 
> (and that includes bug fixes) - so as you say we are just all running 
> around like headless chickens, while Google hopefully has 
> someone calmly sitting there working on the issue (we just dont know about 
> it). One day just to push it into production with little fanfare. 
>
> Google's timescale on fixing issues, is also almost certainly orders of 
> magnitude slower than most people would like. 
>
>
>
>  On Wed, Mar 13, 2013 at 4:17 PM, johnP 
> > wrote:
>
>>
>> Barry -
>>
>> If you look through this message board and at the issue tracker, you'll 
>> see that many people with HRD are also affected by this issue.  
>>
>> As often is the case, the big problem is not the crime - it's the 
>> cover-up.  Everyone here can understand technical issues, if people are 
>> working to fix them.  The non-response from Google is what's freaking 
>> people out.
>>
>>
>>
>>
>> On Wednesday, March 13, 2013 8:31:07 AM UTC-7, barryhunter wrote:
>>
>>>
>>>
>>>
>>> On Wed, Mar 13, 2013 at 9:36 AM, Rafael  wrote:
>>>
 YES! I'm on the master/slave. 

 Google putting a message at the top of the appengine site saying that 
 it's deprecated isn't an excuse for extreme reduction of performance.

>>>
>>> The depreciation pretty much is Google admitting the can't (and/or 
>>> won't) fix M/S. They KNOW it's bad, and want you to stop using it. 
>>>  
>>> M/S is a sinking ship. Google arent allocating much resources to bailing 
>>> it out. They've moved on to brighter and better things. 
>>>
>>>
>>>
 Migrating to HDR will never happen to me. 

>>>
>>> Then you have pretty much resigned yourself to issues. Why are you 
>>> pointing a loaded gun at your own foot?
>>>
>>>
>>>  By continuing to use M/S you making yourself and Google look bad. 
>>>
>>  -- 
>> 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?hl=en
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

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

Re: [google-appengine] 1.7.6 Pre-release SDKs Available

[PK]

Having spent a lot of time with the new server but still using the old one, I 
want to say that the new app server is very promising but I personally think 
the decision to make the new app server the default now is a bit rushed. I hope 
you do not remove the old server before all our bugs have been addressed, this 
should be the criterion not the date. 

In the meantime, where are we supposed to file bugs now that the new server 
becomes the default so we can distinguish between the new and the old server 
issues, can somebody please clarify? 

Thanks,
PK
http://www.gae123.com


On Wednesday, March 13, 2013 at 7:50 AM, Janani Thanigachalam wrote:

> Hello Again Everyone!
> 
> We've posted the pre-release SDKs for Python and Java here:
> http://code.google.com/p/googleappengine/downloads/list
> 
> Please see the pre-release notes below.
> 
> Regards,
> Janani
> 
> App Engine Python SDK - Release Notes
> 
> Version 1.7.6
> ===
> - The new and improved development appserver, which was previewed last 
> release,
>   now becomes the default. The old development appserver has been renamed to
>   old_appserver.py and will remain available until the first release after
>   1 July 2013 when it will be removed from the SDK.
> - The XMPP API now has multi-JID get_presence. This provides the ability to 
> get
>   the availability of multiple users.
> - Django 1.4 and Webob 1.2.3 are now promoted to GA.
> - Apps now have the ability to fopen() files that are declared as static files
>   in app.yaml using the application_readable flag.
> - The dev_appserver now allocates automatic ids using the 'scattered' id
>   allocation policy by default. For more information, please see "Specifying 
> the
>   Automatic ID Allocation Policy":
>   
> https://developers.google.com/appengine/docs/python/tools/devserver#Using_the_
>   Datastore
> - New Search API quotas are now displayed in the Admin Console. These quotas 
> are
>   not currently enforced, but will be part of the pricing model for the Search
>   API in a future release.
> - The experimental Search API's ability to explicitly sort search results by
>   SortExpression.RANK_FIELD_NAME (i.e. _order_id) field in ascending order has
>   been removed.
> - Globally consistent indexes in the experimental Search API are now 
> deprecated
>   and will be removed in the next release.
> - Task Queue tasks may now be added and deleted asynchronously. This allows
>   applications to perform common task queue operations without blocking. This 
> is
>   an experimental feature.
> - In the experimental MapReduce framework, shards that encounter Files API
>   errors will retry three times before the entire job fails.
> - ProtoRPC now supports deserializing and reserializing of unexpected fields.
> - A new ProtoRPC field type for supporting datetime values has been added.
> - Fixed an issue with the new dev_appserver failing on invalid login cookies. 
> It
>   now uses type="email" for email in the login form.
> 
> https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?
> id=36
> - Fixed an issue with the new dev_appserver to have fix_sys_path add the
>   necessary libraries to sys.path making it now compatible with the testbed.
> 
> https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?
> id=45
> 
> 
> 
> 
> 
> App Engine Java SDK - Release Notes
> 
> Version 1.7.6
> =
> - The XMPP API now has multi-JID getPresence(). This provides the ability to 
> get
>   the availability of multiple users.
> - The Java dev_appserver now allocates automatic ids using the 'scattered' id
>   allocation policy by default. For more information, please see "Specifying 
> the
>   Automatic ID Allocation Policy":
>   https://developers.google.com/appengine/docs/java/tools/devserver#Using_the_
>   Datastore
> - New Search API quotas are now displayed in the Admin Console. These quotas 
> are
>   not currently enforced, but will be part of the pricing model for the Search
>   API in a future release.
> - The experimental Search API's ability to explicitly sort search results by
>   SortExpression.RANK_FIELD_NAME (i.e. _order_id) field in ascending order has
>   been removed.
> - Globally consistent indexes in the experimental Search API are now 
> deprecated
>   and will be removed in the next release.
> - Task Queue tasks may now be added and deleted asynchronously. This allows
>   applications to perform common task queue operations without blocking. This 
> is
>   an experimental feature.
> - Fixed an issue that caused NullPointerException in ListIndexesResponse
> http://code.google.com/p/googleappengine/issues/detail?id=8359
> 
> 
> -- 
> 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 
> (mailto:google-appengine+unsubscr

Re: [google-appengine] Re: instances dying is a permanent states for datastore apps?

[johnP]

Or even if Google says that there is not a technical issue; that there have 
been internal tweaks to the scheduler that make instances that (in my case) 
would happily serve for days or weeks to now serve for less than 10-15 
minutes (during a good part of the day); and that we should do a, b, and c 
to maximize performance; that would also provide some clarity.



On Wednesday, March 13, 2013 9:17:17 AM UTC-7, johnP wrote:
>
>
> Barry -
>
> If you look through this message board and at the issue tracker, you'll 
> see that many people with HRD are also affected by this issue.  
>
> As often is the case, the big problem is not the crime - it's the 
> cover-up.  Everyone here can understand technical issues, if people are 
> working to fix them.  The non-response from Google is what's freaking 
> people out.
>
>
>
>
> On Wednesday, March 13, 2013 8:31:07 AM UTC-7, barryhunter wrote:
>>
>>
>>
>>
>> On Wed, Mar 13, 2013 at 9:36 AM, Rafael  wrote:
>>
>>> YES! I'm on the master/slave. 
>>>
>>> Google putting a message at the top of the appengine site saying that 
>>> it's deprecated isn't an excuse for extreme reduction of performance.
>>>
>>
>> The depreciation pretty much is Google admitting the can't (and/or won't) 
>> fix M/S. They KNOW it's bad, and want you to stop using it. 
>>  
>> M/S is a sinking ship. Google arent allocating much resources to bailing 
>> it out. They've moved on to brighter and better things. 
>>
>>
>>
>>> Migrating to HDR will never happen to me. 
>>>
>>
>> Then you have pretty much resigned yourself to issues. Why are you 
>> pointing a loaded gun at your own foot?
>>
>>
>>  By continuing to use M/S you making yourself and Google look bad. 
>>
>

-- 
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] 1.7.6 Pre-release SDKs Available

[Janani Thanigachalam]

Hello Again Everyone!

We've posted the pre-release SDKs for Python and Java here:
http://code.google.com/p/googleappengine/downloads/list

Please see the pre-release notes below.

Regards,
Janani

App Engine Python SDK - Release Notes

Version 1.7.6
===
- The new and improved development appserver, which was previewed last 
release,
  now becomes the default. The old development appserver has been renamed to
  old_appserver.py and will remain available until the first release after
  1 July 2013 when it will be removed from the SDK.
- The XMPP API now has multi-JID get_presence. This provides the ability to 
get
  the availability of multiple users.
- Django 1.4 and Webob 1.2.3 are now promoted to GA.
- Apps now have the ability to fopen() files that are declared as static 
files
  in app.yaml using the application_readable flag.
- The dev_appserver now allocates automatic ids using the 'scattered' id
  allocation policy by default. For more information, please see 
"Specifying the
  Automatic ID Allocation Policy":
  
https://developers.google.com/appengine/docs/python/tools/devserver#Using_the_
  Datastore
- New Search API quotas are now displayed in the Admin Console. These 
quotas are
  not currently enforced, but will be part of the pricing model for the 
Search
  API in a future release.
- The experimental Search API's ability to explicitly sort search results by
  SortExpression.RANK_FIELD_NAME (i.e. _order_id) field in ascending order 
has
  been removed.
- Globally consistent indexes in the experimental Search API are now 
deprecated
  and will be removed in the next release.
- Task Queue tasks may now be added and deleted asynchronously. This allows
  applications to perform common task queue operations without blocking. 
This is
  an experimental feature.
- In the experimental MapReduce framework, shards that encounter Files API
  errors will retry three times before the entire job fails.
- ProtoRPC now supports deserializing and reserializing of unexpected 
fields.
- A new ProtoRPC field type for supporting datetime values has been added.
- Fixed an issue with the new dev_appserver failing on invalid login 
cookies. It
  now uses type="email" for email in the login form.

https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?
id=36
- Fixed an issue with the new dev_appserver to have fix_sys_path add the
  necessary libraries to sys.path making it now compatible with the testbed.

https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?
id=45




App Engine Java SDK - Release Notes

Version 1.7.6
=
- The XMPP API now has multi-JID getPresence(). This provides the ability 
to get
  the availability of multiple users.
- The Java dev_appserver now allocates automatic ids using the 'scattered' 
id
  allocation policy by default. For more information, please see 
"Specifying the
  Automatic ID Allocation Policy":
  
https://developers.google.com/appengine/docs/java/tools/devserver#Using_the_
  Datastore
- New Search API quotas are now displayed in the Admin Console. These 
quotas are
  not currently enforced, but will be part of the pricing model for the 
Search
  API in a future release.
- The experimental Search API's ability to explicitly sort search results by
  SortExpression.RANK_FIELD_NAME (i.e. _order_id) field in ascending order 
has
  been removed.
- Globally consistent indexes in the experimental Search API are now 
deprecated
  and will be removed in the next release.
- Task Queue tasks may now be added and deleted asynchronously. This allows
  applications to perform common task queue operations without blocking. 
This is
  an experimental feature.
- Fixed an issue that caused NullPointerException in ListIndexesResponse
http://code.google.com/p/googleappengine/issues/detail?id=8359

-- 
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] Re: instances dying is a permanent states for datastore apps?

[johnP]

Barry -

If you look through this message board and at the issue tracker, you'll see 
that many people with HRD are also affected by this issue.  

As often is the case, the big problem is not the crime - it's the cover-up. 
 Everyone here can understand technical issues, if people are working to 
fix them.  The non-response from Google is what's freaking people out.




On Wednesday, March 13, 2013 8:31:07 AM UTC-7, barryhunter wrote:
>
>
>
>
> On Wed, Mar 13, 2013 at 9:36 AM, Rafael  >wrote:
>
>> YES! I'm on the master/slave. 
>>
>> Google putting a message at the top of the appengine site saying that 
>> it's deprecated isn't an excuse for extreme reduction of performance.
>>
>
> The depreciation pretty much is Google admitting the can't (and/or won't) 
> fix M/S. They KNOW it's bad, and want you to stop using it. 
>  
> M/S is a sinking ship. Google arent allocating much resources to bailing 
> it out. They've moved on to brighter and better things. 
>
>
>
>> Migrating to HDR will never happen to me. 
>>
>
> Then you have pretty much resigned yourself to issues. Why are you 
> pointing a loaded gun at your own foot?
>
>
>  By continuing to use M/S you making yourself and Google look bad. 
>

-- 
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] problems usually come before new release

[Peter Ondruška]

OK but I prefer being notified about service disruption beforehand and not 
afterwards... ;-) in case upgrade _has_ to be done the way it is done.

On Wednesday, March 13, 2013 2:36:06 PM UTC+1, barryhunter wrote:
>
> Surely this is to be expected. 
>
> Before Google annonnces a new release, it has to be rolled out to all 
> servers. So that when the annoncement is made, the new features can actully 
> be used. 
>
> So that means every single server has to be updated. Which almost 
> certainly means bringing it offline (even for jsut a few seconds) - which 
> means all instances running on it, have to be shutdown. 
>
> They probably dont do single servers at a time, but a whole 
> rack/data-center worth. So while a large number of applications are shifted 
> to a new set of servers, there will be a blip. 
>
> (In fact its explicitly noted the rollout is incremental. If they did a 
> system wide restart, not only would it be an intensive process, doing it 
> incrementally means it can be aborted early should issues be found, before 
> it affects all applications) 
>
>
> Basically every release brings a mass migration, when all applications 
> must be reinitialized on the new system. 
>
>
> (and that is aside from any bugs, or incompatibltities (intentional or 
> otherwise) that a new version may bring) 
>
>
>
>
>
>  On Wed, Mar 13, 2013 at 8:55 AM, Peter Ondruška 
> 
> > wrote:
>
>> Maybe you noticed and maybe it is just rare coincidence but problems we 
>> see usually come before new release(?) Is it only me to observed this? 
>>
>> -- 
>> 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?hl=en
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

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

Re: [google-appengine] Re: instances dying is a permanent states for datastore apps?

[Cesium]

You read the previous posts on this right?

You are complaining about instances lasting an hour?

I'd sacrifice my prize unicorn to get that!
When service goes pear shaped, instances last seconds!

Yes. This behavior will change.
No. You can't predict when the change will occur.
No. There's nothing (effective) you can do.
No. You won't get a response from G.
Yes. You will get used to shoveling unicorn poo.
Yes. It looks like little piles of rainbows.

David

On Wednesday, March 13, 2013 3:36:44 AM UTC-6, Rafael Sanches wrote:
> YES! I'm on the master/slave. 
> 
> 
> Google putting a message at the top of the appengine site saying that it's 
> deprecated isn't an excuse for extreme reduction of performance.
> 
> 
> 
> 
> Migrating to HDR will never happen to me. This is frustrating. 
> 
> 
> 
> On Wed, Mar 13, 2013 at 2:20 AM, timh  wrote:
> 
> 
> Are you running M/S ?
> 
> 
> I just had a look at a different app I have access to on M/S (has large 
> numbers of users) and it appears to be cycling instances fast, and long 
> startup times.
> 
> 
> 
> 
> T
> 
> 
> On Wednesday, March 13, 2013 3:58:22 PM UTC+8, Rafael Sanches wrote:
> 
> 
> 
> You are living the dream my brother. Check this out: 
> http://cl.ly/image/3F0m2c3T1b3D
> 
> 
> 
> 
> It's a screenshot from right now. Please, notice that there's two brave 
> instances that are 1:40 hours old, although we have over 15 that are dying 
> randomly. 
> 
> 
> 
> 
> The best thing is that I am paying a lot for those 15 randomy dying. Also, my 
> 10 million user app is quickly dying just like the instances.. it's 
> beautiful. 
> 
> 
> 
> 
> Alright, 3 days without sleeping. I officially tried everything possible on 
> my side. Now it's just pray for google to fix it.
> 
> 
> 
> 
> 
> On Tue, Mar 12, 2013 at 9:06 PM, timh  wrote:
> 
> 
> 
> 
> Hi
> 
> 
> I am using HRD and usually my resident instances are many days old, however 
> today I have one resident instance 2 hours old, 1 dynamic instance 2 hours 
> old, and a dynamic instance 1.5 days old ;-)
> 
> 
> 
> 
> 
> 
> T
> 
> 
> On Tuesday, March 12, 2013 6:06:15 PM UTC+8, Rafael Sanches wrote:
> 
> 
> 
> Yes, I have a lot of traffic. Out of nothing the instances die and new ones 
> come up. Check out this screenshot: http://cl.ly/image/3e1W1a1d0V3A
> 
> 
> 
> 
> 
> 
> 
> 
> Please, see that some instances are up for more than an hour and a half. 
> Although, many new ones are spawned. 
> 
> 
> You're running on HDR? The may be related to datastore.
> 
> 
> 
> 
> thanks
> rafa
> 
> 
> 
> 
> On Tue, Mar 12, 2013 at 2:34 AM, timh  wrote:
> 
> 
> 
> Do you have billing enabled ?
> idle instance can be shut down at any point where their count is above min 
> idle.  What sort of settings are you running ?
> 
> 
> 
> 
> 
> 
> 
> 
> I have a low traffic site with billing usually 1 or 2 reserved instances 
> (depending on the time of the week.)  All content is dynamic (though cached 
> by memcache) and not seeing any problems at all.
> 
> 
> 
> 
> 
> 
> 
> 
> T
> 
> 
> 
> 
> 
> 
> 
> On Tuesday, March 12, 2013 1:23:35 PM UTC+8, Rafael Sanches wrote:
> 
> 
> 
> 
> 
> 
> Hello,
> 
> 
> 
> I have the application "yumyumlabs" and all of my users are complaining about 
> "slowness" or broken connections.
> 
> 
> 
> 
> 
> 
> 
> 
> To my surprise I went to the appengine console to see that my instances were 
> dying out of nothing. No releases were made on my side and this seems a new 
> behavior. This happening for a week already and I have tried everything.
> 
> 
> 
> 
> 
> 
> 
> 
> I was hopping that this was temporary, but as it turns out it's not. This is 
> the issue: http://code.google.com/p/googleappengine/issues/detail?id=8781
> 
> 
> 
> 
> 
> 
> 
> 
> Can anyone tell me if this will be a new permanent state? All the datastore 
> applications will continue to be this slow? 
> 
> 
> 
> 
> 
> 
> 
> 
> I must take actions ASAP. The current service quality is unbearable. 
> 
> 
> 
> 
> 
> 
> 
> 
> thanks
> rafael
> 
> 
> 
> 
> -- 
> 
> 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?hl=en.
> 
> For more options, visit https://groups.google.com/groups/opt_out.
> 
>  
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> 
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-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?hl=en.
> 
> For more options, visit https://groups.google.com/groups/opt_out.
> 
>  
> 
>  
> 
> 
> 
> 
> 
> 
>

[google-appengine] Re: Converting Google visualization charts to PDF

[Cesium]

Me too.
(At your leisure.)



On Wednesday, March 13, 2013 8:01:31 AM UTC-6, Manoj Kumar wrote:
> Hi,
> 
> 
> I was trying a lot to export(convert) visualization chart to PDF. But, I'm 
> not to do it. Is there any way to do that so? If so, let me know ASAP. 
> 
> 
> Best regards
> Manoj. Siripuram.

-- 
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] Converting Google visualization charts to PDF

[Manoj Kumar]

Hi,

I was trying a lot to export(convert) visualization chart to PDF. But, I'm 
not to do it. Is there any way to do that so? If so, let me know ASAP. 

Best regards
Manoj. Siripuram.

-- 
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] How to know if app version is DEFAULT version?

[Moises Belchin]

Hi guys,

Is there any way to know if a version of my app is the DEFAULT version?

I saw os.environ['DEFAULT_VERSION_HOSTNAME'] and
os.environ['CURRENT_VERSION_ID'] but I didn't find any way to compare two
of them and determine if this current version y the default version.

Thanks for help.

Regards.
Moisés Belchín.

-- 
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] Re: instances dying is a permanent states for datastore apps?

[timh]

Are you running M/S ?

I just had a look at a different app I have access to on M/S (has large 
numbers of users) and it appears to be cycling instances fast, and long 
startup times.

T

On Wednesday, March 13, 2013 3:58:22 PM UTC+8, Rafael Sanches wrote:
>
> You are living the dream my brother. Check this out: 
> http://cl.ly/image/3F0m2c3T1b3D
>
> It's a screenshot from right now. Please, notice that there's two brave 
> instances that are 1:40 hours old, although we have over 15 that are dying 
> randomly. 
>
> The best thing is that I am paying a lot for those 15 randomy dying. Also, 
> my 10 million user app is quickly dying just like the instances.. it's 
> beautiful. 
>
>  Alright, 3 days without sleeping. I officially tried everything possible 
> on my side. Now it's just pray for google to fix it.
>
>
> On Tue, Mar 12, 2013 at 9:06 PM, timh >wrote:
>
>> Hi
>>
>> I am using HRD and usually my resident instances are many days old, 
>> however today I have one resident instance 2 hours old, 1 dynamic instance 
>> 2 hours old, and a dynamic instance 1.5 days old ;-)
>>
>> T
>>
>>
>> On Tuesday, March 12, 2013 6:06:15 PM UTC+8, Rafael Sanches wrote:
>>
>>> Yes, I have a lot of traffic. Out of nothing the instances die and new 
>>> ones come up. Check out this screenshot: http://cl.ly/**
>>> image/3e1W1a1d0V3A 
>>>
>>> Please, see that some instances are up for more than an hour and a half. 
>>> Although, many new ones are spawned. 
>>>
>>> You're running on HDR? The may be related to datastore.
>>>
>>> thanks
>>> rafa
>>>
>>>
>>> On Tue, Mar 12, 2013 at 2:34 AM, timh  wrote:
>>>
 Do you have billing enabled ?
 idle instance can be shut down at any point where their count is above 
 min idle.  What sort of settings are you running ?

 I have a low traffic site with billing usually 1 or 2 reserved 
 instances (depending on the time of the week.)  All content is dynamic 
 (though cached by memcache) and not seeing any problems at all.

 T



 On Tuesday, March 12, 2013 1:23:35 PM UTC+8, Rafael Sanches wrote:
>
>
> Hello,
>
> I have the application "yumyumlabs" and all of my users are 
> complaining about "slowness" or broken connections.
>
> To my surprise I went to the appengine console to see that my 
> instances were dying out of nothing. No releases were made on my side and 
> this seems a new behavior. This happening for a week already and I have 
> tried *everything*.
>
> I was hopping that this was temporary, but as it turns out it's not. 
> This is the issue: http://code.google.com/p/**
> googleappengine/issues/**detai**l?**id=8781
>
> Can anyone tell me if this will be a new permanent state? All the 
> datastore applications will continue to be this slow? 
>
> I must take actions ASAP. The current service quality is unbearable. 
>
>  thanks
> rafael
>
  -- 
 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?hl=en
 .
 For more options, visit 
 https://groups.google.com/**groups/opt_out
 .
  
  

>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-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?hl=en
>> .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

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

[google-appengine] problems usually come before new release

[Peter Ondruška]

Maybe you noticed and maybe it is just rare coincidence but problems we see 
usually come before new release(?) Is it only me to observed this?

-- 
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] Re: Avg Latency and Errors are high recently

[Rafael]

that's probably random that it's back. I have tried that too.

The whole appengine system is highly unreliable at the moment. Right now
all my instances are dying: http://cl.ly/image/3F0m2c3T1b3D

If you keep monitoring it, you will probably find that the issues aren't
fixed.

Please, keep us posted if you find a way.

bye
rafa


On Tue, Mar 12, 2013 at 10:33 PM, GoSharp Lite wrote:

> After I switch back to Java 6, performance is back to normal. Not sure if
> Google has fixed something or Java 7 is causing performance issue.
>
> On Tuesday, March 12, 2013 9:04:28 AM UTC+8, GoSharp Lite wrote:
>>
>> My app is experiencing high latency and errors in the past few days. Avg
>> latency was less than 300ms before, and now it is >5000ms. Does anyone have
>> the same problem?
>>
>  --
> 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.
>
>
>

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