Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Stefano Ciccarelli]

I've observed the same. 
We have a single jar and we disabled the jersey class scanning but the warmup 
still needs 30/35 seconds.

Two weeks ago the startup times were around 15/20 seconds, then, one day (I 
don't remember when) the performance dropped.  

-- 
Stefano Ciccarelli
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Thursday 15 March 2012 at 22:30, Jeff Schnitzer wrote:

> It's hard to be certain, but it *seems* like the biggest delay is
> reading files from whatever it is that passes for a network
> filesystem. I've timed several parts of my app and the only
> reasonable explanation I can come up with is that classloading is
> painfully and erratically slow. This hypothesis is consistent with
> one quirky observed behavior - putting all your classes in a single
> jar file (instead of WEB-INF/classes) has a measurable (beneficial)
> effect on application startup time.
> 
> Jeff
> 
> On Thu, Mar 15, 2012 at 4:09 PM, Emanuele Ziglioli
>  wrote:
> > Has anyone managed to profile cold starts (I don't know whether that's
> > even possible) to see where they take most of the time?
> > Does the length of cold starts on GAE servers correspond to how long
> > it takes on the development server?
> > 
> > I use GAE for Java so what I'll write below reflects that.
> > I know the libraries I use employ annotations and that's got to have
> > an impact. Jaxb (coupled with restlet) for example has got a terrible
> > cold start time.
> > My warmup request does exactly that, it triggers a jaxb warmup. But
> > lately it has been failing. Since that seems to affect mostly the
> > warmup request, users don't seem to be affected terribly (we have very
> > low traffic at this stage though).
> > 
> > I wonder whether the Google Engineers could implement something
> > similar to what Android does: there's a resident Dalvik VM and all new
> > processes fork from it.
> > Our prototype process could have the jvm, the web server and all the
> > rest that's common. Just a thought.
> > 
> > E
> > 
> > --
> > 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.

Re: [google-appengine] Switched to HRD - So far not impressed

[Daniel Kramer]

Yes, I get it. I was anxious to try python27 and jumped the gun early.  But I 
am back to just the HRD switch without python27/threadSafe.  I was not 
surprised to see issue with python27, I didn't expect the errors with just 
switching to HRD.  I also didn't expect to see my backend server appearing to 
run python27 when my app is set to python25

On Mar 15, 2012, at 10:52 PM, Brandon Wirtz wrote:

> Did you skip the day in 4th grade they taught scientific method?
> 
> You don’t change 6 variables at once. Move to HR.
> Test.
> Move to Python 27
> Test.
> Move to Thread Safe
> Test.
>  
> Somewhere in each of those you might want to revise code.  And tweak the 
> scheduler settings. You might want to have more than once version of your app 
> so you can test 2 things at once, like scheduler and Thread safe.
>  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.

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

RE: [google-appengine] Switched to HRD - So far not impressed

[Brandon Wirtz]

Did you skip the day in 4th grade they taught scientific method?

You don't change 6 variables at once. Move to HR.

Test.

Move to Python 27

Test.
Move to Thread Safe

Test.

 

Somewhere in each of those you might want to revise code.  And tweak the
scheduler settings. You might want to have more than once version of your
app so you can test 2 things at once, like scheduler and Thread safe.

 

-- 
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] Switched to HRD - So far not impressed

[Daniel]

I've been running a server for my game SkyWords on AppEngine for a little 
over a year now and never switched over to an HRD server.  I was under the 
impression it cost more but recently learned it doesn't.. so I made the 
switch. 

Prior to switching I had my server running really smoothly, most days I'd 
get zero server errors, some days a small handful.  I swtiched in hopes to 
leverage off python27 and possibly bring the cost of my server down. 
 Since switching I'm getting a lot (hundreds) or errors a day now. 

First I made the switch to python27 and found I was getting multiple server 
errors (mostly DeadlineExceededErrors) so I switched back to python25.  I'm 
still getting multiple (hundreds) of DeadlineExceededErrors using 
python25... Have others found this? could the servers be slower even when 
using python25 causing me to bump up against deadline errors?

I'm also finding some of my cron jobs are failing on my backend server. 
 The logs are showing errors with references to python27, it appears my 
backend is running python27, not python25?  I made sure to kill and 
recreate the backend after double checking my app is set to python25 and 
still seeing the python27 errors.  How do I ensure the backend server is 
also running python25?

I'm really bummed, I can't go back and now I've got to spend serval nights 
debugging what I expected to be a smooth transition. Any advice is 
appreciated

Daniel

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

Re: [google-appengine] Index got stuck - dlzfusion2.appspot.com

[Amy Unruh]

To follow up, this should now be fixed.  (So, you don't need to file the
production issue).

On Fri, Mar 16, 2012 at 2:18 PM, Amy Unruh  wrote:

> hi,
>
> I'll take a look.  To track this, can you file a 'stuck index' production
> issue for your app?
>
> http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
>
>
>
> On Wed, Mar 14, 2012 at 2:26 AM, mel meng  wrote:
>
>> app: dlzfusion2.appspot.com
>> The index has been building for days. Can someone take a look?
>> Thanks.
>>
>> --
>> 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] Google App Engine Pricing

[Chinna]

Hi all,

I'm actually preparing Google Cloud pricing for my firm and a bit
confuse. I need to come out with 3 type of package which is Low,
Likely and High. I checked the Google App Engine - pricing and
features (http://www.google.com/enterprise/cloud/appengine/
pricing.html) and it quite confusing.

How do I know how many instance I need to use for the application?
How I know how many bandwidth used for the application?
How do I get come out with pricing package?

Please advice.

-- 
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: 503 error while compiling my python application during deployment

[Anand Mistry]

Thanks. I'm following up.

On Friday, 16 March 2012 11:51:56 UTC+11, PK wrote:
>
> We filed issue 7155 two hours ago could somebody follow up?
>
> Error 503: --- begin server output ---
>
> Try Again (503)
> An unexpected failure has occurred. Please try again.
> --- end server output ---
>
> Thanks,
> PK
>

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

Re: [google-appengine] Index got stuck - dlzfusion2.appspot.com

[Amy Unruh]

hi,

I'll take a look.  To track this, can you file a 'stuck index' production
issue for your app?
http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue


On Wed, Mar 14, 2012 at 2:26 AM, mel meng  wrote:

> app: dlzfusion2.appspot.com
> The index has been building for days. Can someone take a look?
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

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

Re: [google-appengine] i could not recive the code message

[Amy Unruh]

hi,

You can use the "SMS problems" form linked here:
http://code.google.com/appengine/kb/sms.html#error

On Mon, Mar 12, 2012 at 4:11 PM, 子健 宋 <809882...@qq.com> wrote:

> I'm in china, i could not recive the code message. Please help me
> solve this problem.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

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

Re: [google-appengine] You have sent too many SMS verification messages while trying to create application at Google App Engine

[Amy Unruh]

hi,

You can use the "SMS problems" form linked here:
http://code.google.com/appengine/kb/sms.html#error

On Wed, Mar 14, 2012 at 9:55 AM, PEaCE Lab  wrote:

> hello,
>
> I have non-profit account and my Apps_Enrollment status has been
> Approved.
> I have tried to create an application from google app engine  at
> https://appengine.google.com/start
> but no sms has been sent to me yet and I got following error message.
>
> There were errors:
> Mobile Number or Username
>
> You have sent too many SMS verification messages.
>
> Could you help me to solve this problem?
> thank you so much!
>
> Best regards,
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

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

Re: [google-appengine] Re: BadRequestError: app s~helixchewer cannot access app helixchewer's data during create_bulkloader_config

[Darien Caldwell]

I just ran into this issue. Seems it's still unresolved a year later. :\

On Thursday, March 3, 2011 11:21:56 AM UTC-8, Ikai L (Google) wrote:

> I talked to Jamie about this and there's a bug filed in the issues 
> tracker: 
>
> http://code.google.com/p/googleappengine/issues/detail?id=4671
>
> 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 Wed, Mar 2, 2011 at 1:34 PM, Jamie H  wrote:
>
>> the s~ is affecting what email address I can send email from.  I am
>> now forced to use
>> no-reply@s~APP-ID.appspotmail.com
>>
>> which as far as I know is not an RFC valid email address
>>
>> On Jan 24, 3:21 pm, "Ikai Lan (Google)" 
>> wrote:
>> > Yes, that is the goal. The s~ should not appear anywhere with the 
>> exception
>> > of maybe the admin-console. If it's required anywhere else, that is a 
>> bug we
>> > should address.
>> >
>> > --
>> > 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 Mon, Jan 24, 2011 at 2:12 AM, Waldemar Kornewald <
>> wkornew...@gmail.com>wrote:
>> >
>> > > Will this be fixed, so it's transparent? From an end-user point of 
>> view
>> > > there is no reason to have such a distinction. It only complicates
>> > > everything and people are sending me bug reports about the remote API 
>> not
>> > > working with Django-nonrel when they use the high-replication 
>> datastore. In
>> > > case the s~ prefix will stay, how can I detect this in Django-nonrel 
>> if I
>> > > only know the normal appid and the user doesn't manually specify that 
>> his
>> > > app uses the HR datastore?
>> >
>> > > Bye,
>> > > Waldemar
>> >
>> > > --
>> > > 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<
>> google-appengine%2bunsubscr...@googlegroups.com>
>>  > > .
>> > > For more options, visit this group at
>> > >http://groups.google.com/group/google-appengine?hl=en.
>> >
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/SYqsODK_A_wJ.
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 maintentance periods really have to be during core working hours?

[Greg]

As usual, Brandon, I've got to tip my hat to you - you've come up with
the only good reason to choose MS over HR.

On Mar 15, 4:36 pm, "Brandon Wirtz"  wrote:
> I chose M/S because even more than a mermaid, I want a girl in a Dominatrix
> outfit.
>
> (I got the pool, so I'm one step closer on the Mermaid thing)

-- 
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] DockLayoutPanel, DataGrid and AppEngine — Why doesn't my grid render?

[fastnsilver]

Cross-posting to get more exposure...

I'm not entirely sure this problem is unique to AppEngine, but I don't
have anything else to go on.  Wondering if others have had issues with
applications deployed to Google AppEnginer that mixed MVP4G, GWT-RPC
and Spring MVC?  My issue is around the use of DataGrid in a
DockLayoutPanel (actually within a nested DockLayoutPanel).

Here's the original post:

http://stackoverflow.com/questions/9724730/docklayoutpanel-datagrid-and-appengine-why-doesnt-my-grid-render
DockLayoutPanel, DataGrid and AppEngine — Why doesn't my grid render?

-- 
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] Datastore backup not working, task exits with error code 500

[Daniel Behnen]

Hi,

when trying to create a backup of all my tables, many map reduce tasks 
(>1,000) are spawn but one task does not complete successfully. The 
remaining task calls "POST /_ah/datastore_admin/queue/deferred" and exists 
with error code 500. 
Now there are two stalled tasks in the default queue, one for each backup 
run and the backups do not show up in the backup list.

Is there a way to complete the running backups or to start a successful 
backup?

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

[google-appengine] GAE in China and AppScale

[Artem Nikulchenko]

Hi,

I can't find recent information about that. Are there any changes in
App Engine status in China? Is it still blocked?

If yes - does anybody have an experience in using AppScale project in
real production environment? How easy to maintain AppScale
installation in production environment? How stable is it? How well it
scales? Does anybody have experience in using AppScale in China?

Thanks!

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

Re: [google-appengine] More then 100 complains and no feedback from Google. Was: Outages?

[Enrique]

You are announcing a maintenance of Master/Slave for Monday, but we can do 
in the meantime? Today one of my apps start creating allot of 
instances filling the quota and forcing me to change the billing settings 
to allocate more money.

Enrique

El miércoles 14 de marzo de 2012 17:59:03 UTC-3, Ikai Lan escribió:
>
> Mos,
>
> There have been several responses posted to various threads. I'll go back 
> to those threads and update if there is new information. The disruption to 
> HRD has been posted to the System Status site, and a new maintenance period 
> has been announced on Monday to deal with Master/Slave serving issues (
> https://groups.google.com/forum/?fromgroups#!forum/google-appengine-downtime-notify
> ).
>
> --
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
>
>

-- 
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/-/_MeeR3IzYhQJ.
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: timed out on datastore operations!

[Enrique]

Hi,

>From the last 6 hours I'm experiencing very high latency times in my app. 
Maybe is an AppEngine issue. If you look in AppEngine Status 
page
 and 
compare the chart with yesterday the diference is notable.

Regards,

Enrique

El jueves 15 de marzo de 2012 06:52:07 UTC-3, $ÂÑЀ€P escribió:
>
> Hi,
>
> Any one facing same issues
>
>
> http://code.google.com/status/appengine/detail/datastore/2012/03/15#ae-trust-detail-datastore-get-latency
>  
>
> Or any thing on my ID?
>
> -- 
> Regards
> Sandeep Koduri
> Phone: +91- 99 666 02 456
> Gtalk: sandeep.koduri | Skype: sandeep.koduri
> P Please consider the environment before printing this email 
>
>

-- 
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/-/tfK-NQUuOpgJ.
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] How to restore data from backup?

[Yegor Jbanov]

How do I restore data from a backup?

The documentation (
http://code.google.com/appengine/docs/adminconsole/datastoreadmin.html) is 
no good. The "Completed Operations" section contains my backups, e.g. 
"Backup: datastore_backup_2012_03_15 23 steps Completed". However there is 
no way to "select the backup" and I don't see any "Restore" buttons. I 
tried with and without disabled write operations.

Yegor

-- 
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/-/MQwkpt_5eQ4J.
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: 500 errors + high latency + please communicate with us

[leeflea]

*Nikolai, I just saw your posting of the very same problem I'm having but 
since I just switched browsers yesterday, I just didn't know what to do 
about this. You see, I'm not very computer smart and many of the remarks 
are way over my head as I was merely a Registered Nurse. I, indeed, did 
make a general posting of the problems many of of us are sharing. Thank you 
for posting what you did as I hope someone will help us all.*
*With regards, Leeflea
*
On Friday, March 9, 2012 6:40:20 AM UTC-6, Nikolai wrote:
>
> this is so wrong. I dont see any of these problems reflected in the 
> appengine system status. I don't understand why there is zero communication 
> from google concerning the outages everybody in this forum is seeing right 
> now.
>
> This
>  
> is not a small hickup, but something we (and others) are fighting since 20 
> hours.
> Could someone from google please comment on the current issues und reflect 
> the status on the appengine status page?
>
> thank you!
> nikolai
>

On Friday, March 9, 2012 6:40:20 AM UTC-6, Nikolai wrote:
>
>
> 
> this is so wrong. I dont see any of these problems reflected in the 
> appengine system status. I don't understand why there is zero communication 
> from google concerning the outages everybody in this forum is seeing right 
> now.
> This is not a small hickup, but something we (and others) are fighting 
> since 20 hours.
> Could someone from google please comment on the current issues und reflect 
> the status on the appengine status page?
>
> thank you!
> nikolai
>

On Friday, March 9, 2012 6:40:20 AM UTC-6, Nikolai wrote:
>
>
> 
> this is so wrong. I dont see any of these problems reflected in the 
> appengine system status. I don't understand why there is zero communication 
> from google concerning the outages everybody in this forum is seeing right 
> now.
> This is not a small hickup, but something we (and others) are fighting 
> since 20 hours.
> Could someone from google please comment on the current issues und reflect 
> the status on the appengine status page?
>
> thank you!
> nikolai
>

On Friday, March 9, 2012 6:40:20 AM UTC-6, Nikolai wrote:
>
>
> 
> this is so wrong. I dont see any of these problems reflected in the 
> appengine system status. I don't understand why there is zero communication 
> from google concerning the outages everybody in this forum is seeing right 
> now.
> This is not a small hickup, but something we (and others) are fighting 
> since 20 hours.
> Could someone from google please comment on the current issues und reflect 
> the status on the appengine status page?
>
> thank you!
> nikolai
>

On Friday, March 9, 2012 6:40:20 AM UTC-6, Nikolai wrote:
>
>
> 
> this is so wrong. I dont see any of these problems reflected in the 
> appengine system status. I don't understand why there is zero communication 
> from google concerning the outages everybody in this forum is seeing right 
> now.
> This is not a small hickup, but something we (and others) are fighting 
> since 20 hours.
> Could someone from google please comment on the current issues und reflect 
> the status on the appengine status page?
>
> thank you!
> nikolai
>

On Friday, March 9, 2012 6:40:20 AM UTC-6, Nikolai wrote:
>
>
> 
> this is so wrong. I dont see any of these problems reflected in the 
> appengine system status. I don't understand why there is zero communication 
> from google concerning the outages everybody in this forum is seeing right 
> now.
> This is not a small hickup, but something we (and others) are fighting 
> since 20 hours.
> Could someone from google please comment on the current issues und reflect 
> the status on the appengine status page?
>
> thank you!
> nikolai
>

On Friday, March 9, 2012 6:40:20 AM UTC-6, Nikolai wrote:
>
>
> 
> this is so wrong. I dont see any of these problems reflected in the 
> appengine system status. I don't understand why there is zero communication 
> from google concerning the outages everybody in this forum 

[google-appengine] Error occurring on downloads

[leeflea]

*Hello All,*
*Please pardon my ignorance ( and pardon me if I'm not posting this 
question in the correct place ) as I'm not a very savvy computer user, 
however, I did switch from another browser to Google Chrome yesterday. 
Today I spent some time getting familiar with Google Chrome. A little while 
ago, I downloaded 'Angry Birds' as I've heard so many people speak of it. *
*But I cannot log in to play. I went to a solutions section and one 
suggestion was to 'deselect predict network...' ( I cannot remember the 
rest ) and I did so but still it will not allow me to log in. Now, I can no 
longer find the page where the other solutions were. *
*I read that I could click on a link that would allow me to play locally. I 
clicked on that link and received an error message of: " 500 Error..."*
*Might someone be so kind as to offer some advice, suggestions? As I'm sure 
all of you know so much more than I.*
*Thank you,*
*Leeflea*

-- 
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/-/7yJEXZZjW2UJ.
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: Channel API between front and backend instances

[Jonathan Harris]

Any news on this potential fix?

On Thursday, 28 July 2011 19:56:22 UTC+1, Justin Haugh wrote:
>
> Not at the moment, but we're working on a fix for this, so that a channel 
> created by a frontend can be used by a backend, and vice-versa.  I can't 
> provide an exact release date at this point, but it likely will be in one 
> of the next few releases.
>
> Until then, the suggested method of handling this is to have either your 
> frontend or backend be responsible for Channel communication, and use 
> another mechanism for communication between FE and BE, such as urlfetch, 
> memcache, the datastore, or the task queue.
>
> Justin
>

On Thursday, 28 July 2011 19:56:22 UTC+1, Justin Haugh wrote:
>
> Not at the moment, but we're working on a fix for this, so that a channel 
> created by a frontend can be used by a backend, and vice-versa.  I can't 
> provide an exact release date at this point, but it likely will be in one 
> of the next few releases.
>
> Until then, the suggested method of handling this is to have either your 
> frontend or backend be responsible for Channel communication, and use 
> another mechanism for communication between FE and BE, such as urlfetch, 
> memcache, the datastore, or the task queue.
>
> Justin
>

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

Re: [google-appengine] Re: Problem with mail quota

[Bogdan Nourescu]

I have the same problem. I made an app for sending many emails to a list of 
customers.
I enabled billing for 11$/day, I've imported in the app all the customers 
(~300k datastore writes and 20  Frontend Instance Hours )
My app is "cbn-newsletter"
I've enabled billing today and i intend to send a lot of mails in the next 
2 days.
Can i force a charge to be send? Or can you take money from my account 
beforehand?

I already pay another app from the same credit card for about ~5$/week


On Wednesday, March 14, 2012 6:53:47 PM UTC+2, Christina Ilvento wrote:
>
> Hi All,
>
> We recently made a change that causes the 100 email/day quota to only be 
> lifted once a charge has been successfully cleared. Did you recently enable 
> billing, or has billing been enabled for more than one week?
>
>
> Thanks,
> Christina
>
> On Tue, Mar 13, 2012 at 8:46 PM, Daniel  wrote:
>
>> I'm seeing the same problem! I have hit 100 emails and can't mail anymore 
>> even with a very generous billing quota per day.. billable email is not 
>> triggering.  
>>
>> My app is sky-words-hrd
>>
>>
>>
>> On Wednesday, February 8, 2012 2:36:40 PM UTC-8, Ice13ill wrote:
>>>
>>> In SDK 1.6.2 is stated that: 
>>>  "Mail Quota for App Engine apps that have signed up for billing 
>>> will only be increased after the first payment for the app is 
>>> processed. " 
>>>
>>> In the documentation I found this: 
>>> "100 recipients until first charge cleared; 2000 recipients free and 
>>> no maximum thereafter" 
>>>
>>> The problem is that my app has billing enabled for a very long time 
>>> and although everything was ok until today (i also checked the billing 
>>> history and emails that exceeded the 100 limit were billed 
>>> correctly) , now my app has reached 100 mail quota and it cannot send 
>>> any more emails... 
>>>
>>> Does anyone else has this problem ?
>>
>>  -- 
>> 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/-/AYlR59U_ChkJ.
>>
>> 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.
>>
>
>
>
> -- 
>
> Christina Ilvento | Google App Engine | cilve...@google.com |
>  (650)-201-9399
>
>
>  

-- 
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/-/7CLrHqWH4YcJ.
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] i could not recive the code message

[子健 宋]

I'm in china, i could not recive the code message. Please help me
solve this problem.

-- 
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] You have sent too many SMS verification messages while trying to create application at Google App Engine

[PEaCE Lab]

hello,

I have non-profit account and my Apps_Enrollment status has been
Approved.
I have tried to create an application from google app engine  at
https://appengine.google.com/start
but no sms has been sent to me yet and I got following error message.

There were errors:
Mobile Number or Username

You have sent too many SMS verification messages.

Could you help me to solve this problem?
thank you so much!

Best regards,

-- 
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] Experiencing Uncaught exception from servlet com.google.apphosting.runtime.HardDeadlineExceededError since yesterday

[David Engelmaier]

Hello,

We have been experiencing problems with our game backend since
yesterday, just PMF init takes 6 seconds and some
queries don't get finished, we are getting Uncaught exception from
servlet com.google.apphosting.runtime.HardDeadlineExceededError
for heavier calls. Just fetch object request takes 15 seconds to
finish, I have started optimizing caching with memcache where
possible,
but still have problems running the app, sometimes it finishes within
the timeframe, sometimes not.

appid:fishingbablo
datastore:hdr
language:Java
datastore entities:JDO

Many thanks for your help

David Engelmaier

PS
I see jruby apps of mine and others failing to start at all since
yesterday.

-- 
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] Quota issues - Data usage jumped to 100%

[Connor Dunn]

My app has been growing slowly over a couple of years and is around 70% of 
the free datastore usage allowed, today however it jumped to 100% and I'm 
getting quota denials. It did this before and I enabled billing, which 
fixed the problem, but after a few days the usage dropped down to 70% again.

In the billing history I was never billed for the quota being over 100% 
(despite it showing as over 100% in the dashboard. This meant according to 
the billing history I never needed more than the free quota, but I had to 
enable billing and pay the minimum billing amount for my app to keep 
running (rather annoying). After this seemed to go away I disabled billing, 
but now, some time later it's happened again.

I have again enabled billing as I want my app to function, but I was 
wondering what was going on here, is it a bug or is something happening 
that I don't understand?

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/-/PxTANMKS2JYJ.
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] Calling Javascript (or ScriptEditor) functions from Spreadsheet Cell

[arun]

I have not been able to find this in the Google Docs Spreadsheet
documentation. Maybe someone here can help.

In Google Docs Spreadsheet, is it possible to use a Javascript
function in the formula of a cell. Say for instance, I want to use the
Javascript function encodeURIComponent() on the contents of a cell,
something like, "=encodeURIComponent(A1)", where it produces the
result of URL encoding the value at A1.

Can this be done? This could be generalized a bit more. What if I'd
like to call a function in my own script? I know how to attach a
script editor function to an event. I'd like to be able to call it
from a formula.

Arun

-- 
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] Index got stuck - dlzfusion2.appspot.com

[mel meng]

app: dlzfusion2.appspot.com
The index has been building for days. Can someone take a look?
Thanks.

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

Re: [google-appengine] yet another pending latency question

[Thomas]

We're facing exactly the same problems: appengine scheduler was, and 
unfortunately, still is a pain. Google should really get this fixed because 
it is a major problem for almost every app running there.
Thanks for your suggestion, we will give it a try. 


Am Sonntag, 11. März 2012 07:14:56 UTC+1 schrieb Jeff Schnitzer:
>
> You probably aren't going to like this tip but:
>
> I find that any deviation from Auto/Auto produces a horrible UX.  I
> haven't done a great deal of experimentation but all preliminary
> results have been bad - lots of unnecessary instance starts, many of
> which block user-facing requests.  All on a nearly idle application.
> At this point I have taped over those sliders like you would a
> lightswitch: DO NOT TOUCH.
>
> The behavior of the scheduler is opaque, so those sliders act as
> unpredictable inputs to a chinese puzzle whose only perceptible
> outputs are tortured screams from your website visitors.  It's hard to
> imagine a way to win at this game.
>
> Some official transparency as to the actual behavior of the scheduler
> would help out a lot.
>
> Jeff
>
> On Sat, Mar 10, 2012 at 9:23 PM, Peter Warren  
> wrote:
> > I'm trying to understand why app engine spawns new instances of our
> > app given our settings and a miniscule load of 7 requests from one
> > client.
> >
> > Our application settings are:
> > min idle instances: 3
> > max idle instances: 3
> > min pending latency: 15 secs
> > max pending latency: automatic
> >
> > We run a client-based web app that initially makes a series of
> > requests to our app engine instance(s). In the case I'm concerned with
> > there are 7 requests that all take well under 15 seconds. According to
> > the app engine instance logs the times are: 36ms, 207ms, 52ms, 160ms,
> > 624ms, 1405ms, 3232ms.
> >
> > There are no other requests being executed against that app; all the
> > response times are *well* under 15 seconds, and yet app engine spawns
> > 3 new app instances. Why?
> >
> > In fact the app engine logs show 6 requests being serviced, then 1 new
> > app instance spawned, then the 7th request serviced, then another 2
> > app instances spawned.
> >
> > Our app gets very little traffic, but when a new client app is loaded
> > in a browser somewhere between 3 & 7 requests are sent to app engine.
> > I'm trying to keep app engine from launching new instances of our app
> > since the 3 resident instances should be more than capable of handling
> > our traffic volume, and spawning new instances kills the response
> > time.
> >
> > Thanks for any tips!
> >
> > Peter
> >
> > --
> > You received this message because you are subscribed to the Google 
> Groups "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to 
> google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at 
> http://groups.google.com/group/google-appengine?hl=en.
> >
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/ByuQS79prYMJ.
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] 503 error while compiling my python application during deployment

[PK]

We filed issue 7155 two hours ago could somebody follow up?

Error 503: --- begin server output ---

Try Again (503)
An unexpected failure has occurred. Please try again.
--- end server output ---

Thanks,
PK

-- 
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/-/XNoRHq5ys28J.
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: More then 100 complains and no feedback from Google. Was: Outages?

[johnP]

Wonderful writing!!!  You should receive a Pullet surprise!!!



On Mar 15, 4:26 pm, "Brandon Wirtz"  wrote:
> > Thanks alot, Brandon, for the excellent advice.
>
> I am considering making an auto responder:
>
> Dear Google App Engine Patron,
>
> Thank you for your inquiry about why your GAE experience sucks.  It appears
> from your posting that you are running on Master Slave.  We regret to inform
> you that any issues you have are related to this decision which you made
> early on in your work with GAE and you will continue to regret this decision
> until you move to High Replication.  If you are unwilling, or unable to move
> off of Master / Slave we make the following suggestions:
>
> Make a Funny Custom Error page with lots of pop-ups so that you can monetize
> your downtime.
> Mark scheduled downtimes on the calendar in advance and claim they are
> religious holidays (Google is God, and if God is resting so should you)
> Modify your code to work in a read only, mode so that maintenance has
> minimal impact.
> Put Migration to High Replication on your roadmap, schedule a vacation
> during the month the migration is scheduled to take place so it is someone
> else's problem.
>
> In the unlikely event that you still believe the Master Slave offers the
> best choice for your application we might suggest you visit a psychiatrist,
> or a neurologist as clearly your brain is also experiencing some sort of
> malfunction.  We are aware that Master Slave sounds much sexier than High
> Replication. We are also aware that replication is what threatened the SyFy
> Stargate:SG1 Universe, but we remind you that was a work of fiction.
>
> Have a great day, and we thank you for your continued patronage.
>
> Google App Engine Volunteer Support (We are in no way affiliated with
> Google, and we don't really volunteer any support)
>
> PS
> Did you like that marketing thing Google did where they pre-select High
> Replication, then on the Master Slave description imply that Master Slave
> will cost 1/3 as much, but with downtime and performance issues it actually
> costs more? Yeah, we wish we thought of it too. We'd do similar things with
> our marketing but Google probably patented it.

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

Re: [google-appengine] Re: More then 100 complains and no feedback from Google. Was: Outages?

[Jeff Schnitzer]

On Thu, Mar 15, 2012 at 7:36 PM, toonetown  wrote:
> So, explain this to me...is this only a master/slave issue, and those with 
> high replication data store aren't seeing the harddeadlinexceeded exceptions? 
> That wouldn't make sense in our case, as we use absolutely no data store 
> functionality.
>
> I'd be willing to migrate my app if it would make any difference...but I 
> can't see how it would be any different.

The difference is that Google actually cares about uptime on the HRD.

Jeff

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

RE: [google-appengine] Re: More then 100 complains and no feedback from Google. Was: Outages?

[Brandon Wirtz]

> I'd be willing to migrate my app if it would make any difference...but I
can't see how it would be any different.

I tested this. Hello world is down a LOT on MS, and is almost never down on
HR.

Even Static files go down on MS and basically never go down on HR (Except
when Edge or AppsForDomains has issues)



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

RE: [google-appengine] Re: More then 100 complains and no feedback from Google. Was: Outages?

[toonetown]

So, explain this to me...is this only a master/slave issue, and those with high 
replication data store aren't seeing the harddeadlinexceeded exceptions? That 
wouldn't make sense in our case, as we use absolutely no data store 
functionality.

I'd be willing to migrate my app if it would make any difference...but I can't 
see how it would be any different.

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

RE: [google-appengine] Re: More then 100 complains and no feedback from Google. Was: Outages?

[Brandon Wirtz]

> Thanks alot, Brandon, for the excellent advice.

I am considering making an auto responder:

Dear Google App Engine Patron,

Thank you for your inquiry about why your GAE experience sucks.  It appears
from your posting that you are running on Master Slave.  We regret to inform
you that any issues you have are related to this decision which you made
early on in your work with GAE and you will continue to regret this decision
until you move to High Replication.  If you are unwilling, or unable to move
off of Master / Slave we make the following suggestions:

Make a Funny Custom Error page with lots of pop-ups so that you can monetize
your downtime.
Mark scheduled downtimes on the calendar in advance and claim they are
religious holidays (Google is God, and if God is resting so should you)
Modify your code to work in a read only, mode so that maintenance has
minimal impact.
Put Migration to High Replication on your roadmap, schedule a vacation
during the month the migration is scheduled to take place so it is someone
else's problem.

In the unlikely event that you still believe the Master Slave offers the
best choice for your application we might suggest you visit a psychiatrist,
or a neurologist as clearly your brain is also experiencing some sort of
malfunction.  We are aware that Master Slave sounds much sexier than High
Replication. We are also aware that replication is what threatened the SyFy
Stargate:SG1 Universe, but we remind you that was a work of fiction.

Have a great day, and we thank you for your continued patronage.

Google App Engine Volunteer Support (We are in no way affiliated with
Google, and we don't really volunteer any support)

PS
Did you like that marketing thing Google did where they pre-select High
Replication, then on the Master Slave description imply that Master Slave
will cost 1/3 as much, but with downtime and performance issues it actually
costs more? Yeah, we wish we thought of it too. We'd do similar things with
our marketing but Google probably patented it.




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

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Jeff Schnitzer]

On Thu, Mar 15, 2012 at 6:17 PM, Emanuele Ziglioli
 wrote:
>
> have you got experience with Amazon or Heroku, with regards to cold
> startup time?
> Is it more predictable?

Sure, EC2 is predictable... it takes several minutes (plural) to spin
up a VM and then your app.  Remember, in EC2-land you have to wait for
the OS to boot before your web application can start loading.

No thanks.

20-second cold start times are annoying but not particularly terrible,
as long as users don't have to see them.  I feel confident that Goog
will eventually fix whatever it is misrouting user requests to unready
instances.  In the mean time, I've found that I can get very good
performance by:

 * Using Auto/Auto
 * Deploying new code to a new version, hitting that new version to
warm it up, then switching default versions

I'd really like to automate this second step.

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: Javaland scheduler behavior

[Mauricio Aristizabal]

Woah it's working great for me today! Apparently because my changes to 
enable edge-caching finally kicked in overnight (I used Brandon Wirtz's 
excellent instructions 
here).
 
 So now I have only one dyno instance and it doesn't seem to ever create a 
second one even though setting is auto/auto.

Which makes sense: now a new user page load results in 2 request (html and 
ajax call) vs 40 (including static resources).  I still see the static 
requests in logs, but with a 204 instead of 304, and taking consistently 
about 23ms instead of up to couple hundred depending on file size. So they 
probably return so quickly the queue never grows much if at all. 
Interestingly, the Requests count in the instances page only increases by 2 
(so not reporting the served 204s).

Last thing: My static cache settings filter sets a random expiry between 5 
and 6 minutes, so even though every couple minutes a resource will actually 
have to be served, it's one at a time:

resp.setHeader("Cache-Control", "public, max-age=3" + 
Math.round(Math.random()*9) + "0");
resp.setHeader("Pragma", "Public");

Hope this helps!



On Wednesday, March 14, 2012 11:24:00 PM UTC-7, Mauricio Aristizabal wrote:
>
> I'm experiencing the same issues and it's a shame: It feels like Google 
> designed an F1 race car here, and then limited top speed to 20mph.
>>
>>
> What good is this shiny platform, full of slick, ready-to-use APIs and the 
> promise of automatic elasticity, if a simple page often takes 40 seconds to 
> load, and there is little you can do about it?
>
> Further this doesn't seem like a complex algorithm but a simple rule: 
> don't add any request to a new instance's queue until the warmup request 
> returns (and it is marked available / added to the pool).
>
> I really, really, hope this is a bug that will be addressed soon (and that 
> release processes are improved so others like it are never introduced).
>
> Either way, unfortunately between this and the last few days' issues AE is 
> not looking very enterprise-ready at all, and I now have to consider it a 
> risk rather than a highlight in my business plan and investor pitch.
>
> Mauricio
> Founder, 
> commentous.com
>

-- 
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/-/TRueldNlVTUJ.
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: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Emanuele Ziglioli]

Hi Jeff,

have you got experience with Amazon or Heroku, with regards to cold
startup time?
Is it more predictable?
Perhaps having control over it means one could implement cold starts
in a more clever way.
Hint, hint for anyone!

On Mar 16, 10:30 am, Jeff Schnitzer  wrote:
> It's hard to be certain, but it *seems* like the biggest delay is

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

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Claude Zervas]

My app uses MS with python 2.5 and initially I was trying to maximize cold 
start performance as cheaply as possible by setting min instances = 1 and 
max = 2, but I was getting huge latencies due to requests getting routed to 
cold starts which then led to over quota errors. I then set max instances = 
1 and performance more than doubled and no more over quota problems... 
weird. It seems having just one always hot instance bypasses the 
scheduler's odd behavior.

I think GAE is great if you have a fairly large budget but it just isn't a 
viable platform for low traffic (and low budget) applications given the 
unpredictable performance and almost zero support. The idea of 
automatically spinning up instances to handle traffic spikes is great, but 
in practice it seems to be really expensive and leads to spurious latency 
issues. I've been using GAE since 2009 and it's been really great to use, 
especially when it was free, but now I'm thinking an EC2 instance with 
Appscale might not be such a bad thing and possibly less of a hassle in the 
long run... I suspect Google would rather see apps like mine go away anyway 
since they don't generate much income.



On Thursday, March 15, 2012 9:41:53 AM UTC-7, prashant wrote:
>
> Almost identical setup and observations. 
>
> In addition,
>
> We are observing that one instance with very few warmups (spin offs of new 
> instances) can be achieved with *min instances = auto and max = 1. *Our 
> traffic is not that much ~ 1 QPS with mostly < 1 s latency
>
>
> Thanks
> Prashant
>

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

Re: [google-appengine] Storing from PDF to IMG

[Stuart Langley]

http://code.google.com/appengine/docs/python/blobstore/overview.html#Writing_Files_to_the_Blobstore

On Friday, 16 March 2012 03:03:21 UTC+11, Max wrote:
>
> Where is the file api?
> Sorry, I can't understand what you refer to. Could you please push me in 
> the right direction?
>
> Il giorno giovedì 15 marzo 2012 16:34:51 UTC+1, Jeff Schnitzer ha scritto:
>>
>> You must use the Files API to write the generated image to the blobstore.
>>
>> Jeff
>>
>> On Thu, Mar 15, 2012 at 6:16 AM, Max  
>> wrote:
>> > Dear All,
>> > I'm always storing the img I receive in the blobstore using this code:
>> >
>> > class UploadHandler(blobstore_handlers.BlobstoreUploadHandler):
>> >  def post(self):
>> >  upload_files = self.get_uploads('File')
>> >  blob_info = upload_files[0]
>> >  fotos = FOTO()
>> >  fotos.link = blob_info.key()
>> >  fotos.Tlink = images.get_serving_url(fotos.link, 94)
>> >  fotos.Glink = images.get_serving_url(fotos.link, 800)
>> >  fotos.put()
>> >
>> > Now I receive a PDF and I have to store an IMG.
>> > And I'm thinking to use the conversions tool as per below.
>> >
>> > from google.appengine.api import conversion
>> >
>> > # Create a conversion request from HTML to PNG.
>> > asset = conversion.Asset("text/html", "some data", "test.html")
>> > conversion_obj = conversion.Conversion(asset, "image/png")
>> >
>> > result = conversion.convert(conversion_obj)
>> > if result.assets:
>> >   # Note: in most cases, we will return data all in one asset.
>> >   # Except that we return multiple assets for multiple pages image.
>> >   for asset in result.assets:
>> > doSomethingWithAsset(asset.data)
>> > else:
>> >   handleError(result.error_code, result.error_text)
>> >
>> >
>> > My question is:
>> > How can I store the asset? Could I still use the way I was?
>> >
>> > Thanks
>> >
>> > Max
>> >
>> > --
>> > 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/-/BDSZMmVUHJAJ.
>> > To post to this group, send email to google-appengine@googlegroups.com.
>> > To unsubscribe from this group, send email to
>> > google-appengine+unsubscr...@googlegroups.com.
>> > For more options, visit this group at
>> > http://groups.google.com/group/google-appengine?hl=en.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/G_fsqTBrtdIJ.
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: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Kyle Finley]

The interesting thing about cold start time, is that it seems to varies 
based on the AppID, at least with the Python27 runtime.

As stated here ( 
https://groups.google.com/forum/?fromgroups#!topic/google-appengine/W7EJrBhHEJg 
) I tested the exact same application on multiple AppIDs and discovered 
that a new AppID started my application in less then half the time (63% 
faster) then an older one.

I would be interested to hear if this is unique to my application or is 
true for others.

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

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Jeff Schnitzer]

It's hard to be certain, but it *seems* like the biggest delay is
reading files from whatever it is that passes for a network
filesystem.  I've timed several parts of my app and the only
reasonable explanation I can come up with is that classloading is
painfully and erratically slow.  This hypothesis is consistent with
one quirky observed behavior - putting all your classes in a single
jar file (instead of WEB-INF/classes) has a measurable (beneficial)
effect on application startup time.

Jeff

On Thu, Mar 15, 2012 at 4:09 PM, Emanuele Ziglioli
 wrote:
> Has anyone managed to profile cold starts (I don't know whether that's
> even possible) to see where they take most of the time?
> Does the length of cold starts on GAE servers correspond to how long
> it takes on the development server?
>
> I use GAE for Java so what I'll write below reflects that.
> I know the libraries I use employ annotations and that's got to have
> an impact. Jaxb (coupled with restlet) for example has got a terrible
> cold start time.
> My warmup request does exactly that, it triggers a jaxb warmup. But
> lately it has been failing. Since that seems to affect mostly the
> warmup request, users don't seem to be affected terribly (we have very
> low traffic at this stage though).
>
> I wonder whether the Google Engineers could implement something
> similar to what Android does: there's a resident Dalvik VM and all new
> processes fork from it.
> Our prototype process could have the jvm, the web server and all the
> rest that's common. Just a thought.
>
> E
>
> --
> 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: Javaland scheduler behavior

[Max Völkel]

We are also very often very confused about the scheduler and hope GAE will 
fix this soon.
>
>

-- 
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/-/smX6H4DCSYUJ.
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: More then 100 complains and no feedback from Google. Was: Outages?

[johnP]

Thanks alot, Brandon, for the excellent advice.


On Mar 15, 1:27 pm, "Brandon Wirtz"  wrote:
> >> b.  Will we get refunded for the excess charges?
>
> There is no SLA on M/S
> Move to HR

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

RE: [google-appengine] Re: More then 100 complains and no feedback from Google. Was: Outages?

[Brandon Wirtz]

>> b.  Will we get refunded for the excess charges?

There is no SLA on M/S
Move to HR





-- 
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: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Emanuele Ziglioli]

Has anyone managed to profile cold starts (I don't know whether that's
even possible) to see where they take most of the time?
Does the length of cold starts on GAE servers correspond to how long
it takes on the development server?

I use GAE for Java so what I'll write below reflects that.
I know the libraries I use employ annotations and that's got to have
an impact. Jaxb (coupled with restlet) for example has got a terrible
cold start time.
My warmup request does exactly that, it triggers a jaxb warmup. But
lately it has been failing. Since that seems to affect mostly the
warmup request, users don't seem to be affected terribly (we have very
low traffic at this stage though).

I wonder whether the Google Engineers could implement something
similar to what Android does: there's a resident Dalvik VM and all new
processes fork from it.
Our prototype process could have the jvm, the web server and all the
rest that's common. Just a thought.

E

-- 
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: More then 100 complains and no feedback from Google. Was: Outages?

[johnP]

My app is responding 10x slower than usual, and # of instances is up
about 5-8x.  My daily costs are 10x usual, and I am at risk of
exceeding my daily quota.

I am on M/S.

Question:
a.  Do I need to expand my quota to cover these additional charges
(shutting down is not an option).
b.  Will we get refunded for the excess charges?
c.  My appid is thinkwave3; can it be moved back to a legacy serving
platform?

Thank you.

johnP



On Mar 15, 12:48 pm, toonetown  wrote:
> That's great!  I mis-read that comment before, and thought it had to do
> with a billing issue or High-replication datastore.  (Mos's question
> appeared to be about billing, and the response seemed to indicate something
> with the HRD - which we are not using HRD).
>
> I'm glad that there is actually some work going in to this...
>
> -Nathan
>
>
>
>
>
>
>
> On Thursday, March 15, 2012 1:35:27 PM UTC-6, Rick Mangi wrote:
>
> > They have responded. Look at the last comment in the thread before yours.
> > I'm not trying to defend them by any means, I think the lack of response
> > from google in general is quite disturbing, but Ikai did reply finally
> > saying that they are working on it.
>
> > On Thursday, March 15, 2012 1:59:45 PM UTC-4, toonetown wrote:
>
> >> Yes - we are still seeing problems too - I think it is ridiculous that we
> >> aren't hearing anything about the issue from Google...how they are planning
> >> on addressing it, etc.
>
> >> There are over 15 bugs that are similar to
> >>http://code.google.com/p/googleappengine/issues/detail?id=7133- all
> >> have been logged in the past 2 weeks, so that tells me that *SOMETHING* is
> >> wrong...
>
> >> -Nathan
>
> >> On Wednesday, March 14, 2012 9:42:21 AM UTC-6, Mos wrote:
>
> >>> Problem still exists: High latency and a significant number of requests
> >>> fail or result in uncontrolled creation of new instances.
>
> >>> GAE customers complain and complain for days.  It seems like many
> >>> website have to accept that the 500-error is an integral feature of the 
> >>> GAE
> >>> run-time.
> >>> Even worse:  The broken platform leads to increase usage of instances
> >>> and therefore leads to higher costs for paying customer.
>
> >>> No communication from Google; no feedback on the mailing list; no status
> >>> updates on the issue tracker.
> >>> Instead a always green status:  http://code.google.com/status/appengine
> >>> (I think the GAE community needs to develop a crowed sources status page 
> >>> to
> >>> get a picture what's really is going on)
>
> >>> That makes me crazy.  I saw many platforms and business support forums
> >>> the last years, but never encountered such an ignorance regarding custom
> >>> complains.
>
> >>> The only official response I saw, was the "Escalated your issue to the
> >>> reliability team" in one of the related issues:
> >>>http://code.google.com/p/googleappengine/issues/detail?id=7133
>
> >>> So, 'realiability team' what's going on? How is the status?
>
> >>> On Tue, Mar 13, 2012 at 3:22 PM, Mos  wrote:
>
>  > What is your application id?
>
>  krisen-talk    (www.krisentalk.de)
>
>  > Feel free to open a production issue
>
>  There is already an issue from someone else (following this thread a
>  lot of people are affected):
>
> http://code.google.com/p/googleappengine/issues/detail?id=7133
>
>  Johan, what's going on with GAE the last days?  It doesn't feel like a
>  PaaS in production mode.
>  Perhaps Google should reintroduce the Beta status. ;)
>
>  On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine 
>  wrote:
>
> > What is your application id?
>
> > Feel free to open a production issue, if you want to investigate this
> > offthread:
>
> >http://code.google.com/p/googleappengine/issues/entry?template=Produc...
>
> > On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:
>
> >> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one
> >> instance, no new deployment, simple page just hitting MemCache):
>
> >> "Request was aborted after waiting too long to attempt to service
> >> your request."   -->  User sees 500er
>
> >> GAE-Team, what is going on the last days?  In my opinion the Google
> >> App Engine is unreliable and looks more like a alpha- or beta-
> >> cloudenvrionment
>
> >> Please Google share you analysis with us.
>
> >> Cheers
> >> Mos
>
> >> 2012/3/13 Sébastien Tromp 
>
> >>> Hello,
>
> >>> Same thing here, since around an hour ago:
> >>> AppID: fiveorbsgame & fiveorbsgame-test
>
> >>> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov 
> >>> wrote:
>
>  I'm encountering the same issue with HR app. The spike got started
>  in about ~1 hour from now.
>
>  AppID: cmsevobg
>  Datastore: HR
>
>  On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> > In case you're keeping track of issues thinking it's generally
> > cleared up:
>
> 

[google-appengine] Re: More then 100 complains and no feedback from Google. Was: Outages?

[toonetown]

That's great!  I mis-read that comment before, and thought it had to do 
with a billing issue or High-replication datastore.  (Mos's question 
appeared to be about billing, and the response seemed to indicate something 
with the HRD - which we are not using HRD).

I'm glad that there is actually some work going in to this...

-Nathan

On Thursday, March 15, 2012 1:35:27 PM UTC-6, Rick Mangi wrote:
>
> They have responded. Look at the last comment in the thread before yours. 
> I'm not trying to defend them by any means, I think the lack of response 
> from google in general is quite disturbing, but Ikai did reply finally 
> saying that they are working on it.
>
> On Thursday, March 15, 2012 1:59:45 PM UTC-4, toonetown wrote:
>>
>> Yes - we are still seeing problems too - I think it is ridiculous that we 
>> aren't hearing anything about the issue from Google...how they are planning 
>> on addressing it, etc.
>>
>> There are over 15 bugs that are similar to 
>> http://code.google.com/p/googleappengine/issues/detail?id=7133 - all 
>> have been logged in the past 2 weeks, so that tells me that *SOMETHING* is 
>> wrong...
>>
>> -Nathan
>>
>> On Wednesday, March 14, 2012 9:42:21 AM UTC-6, Mos wrote:
>>>
>>> Problem still exists: High latency and a significant number of requests 
>>> fail or result in uncontrolled creation of new instances.
>>>
>>> GAE customers complain and complain for days.  It seems like many 
>>> website have to accept that the 500-error is an integral feature of the GAE 
>>> run-time.
>>> Even worse:  The broken platform leads to increase usage of instances 
>>> and therefore leads to higher costs for paying customer.
>>>
>>> No communication from Google; no feedback on the mailing list; no status 
>>> updates on the issue tracker. 
>>> Instead a always green status:   http://code.google.com/status/appengine
>>>  
>>> (I think the GAE community needs to develop a crowed sources status page to 
>>> get a picture what's really is going on)
>>>
>>> That makes me crazy.  I saw many platforms and business support forums 
>>> the last years, but never encountered such an ignorance regarding custom 
>>> complains. 
>>>
>>> The only official response I saw, was the "Escalated your issue to the 
>>> reliability team" in one of the related issues:
>>> http://code.google.com/p/googleappengine/issues/detail?id=7133 
>>>
>>> So, 'realiability team' what's going on? How is the status?
>>>
>>>
>>>
>>> On Tue, Mar 13, 2012 at 3:22 PM, Mos  wrote:
>>>
 > What is your application id?

 krisen-talk(www.krisentalk.de)


 > Feel free to open a production issue

 There is already an issue from someone else (following this thread a 
 lot of people are affected):

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

 Johan, what's going on with GAE the last days?  It doesn't feel like a 
 PaaS in production mode.
 Perhaps Google should reintroduce the Beta status. ;)  


 On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine wrote:

> What is your application id?
>
> Feel free to open a production issue, if you want to investigate this 
> offthread:
>
> http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
>
>
> On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:
>
>> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one 
>> instance, no new deployment, simple page just hitting MemCache):
>>
>> "Request was aborted after waiting too long to attempt to service 
>> your request."   -->  User sees 500er
>>
>> GAE-Team, what is going on the last days?  In my opinion the Google 
>> App Engine is unreliable and looks more like a alpha- or beta- 
>> cloudenvrionment
>>
>> Please Google share you analysis with us.
>>
>> Cheers
>> Mos
>>
>>  
>>
>>  
>>
>> 2012/3/13 Sébastien Tromp 
>>
>>> Hello,
>>>
>>> Same thing here, since around an hour ago:
>>> AppID: fiveorbsgame & fiveorbsgame-test
>>>
>>>
>>> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov wrote:
>>>
 I'm encountering the same issue with HR app. The spike got started 
 in about ~1 hour from now. 

 AppID: cmsevobg
 Datastore: HR

 On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>
> In case you're keeping track of issues thinking it's generally 
> cleared up:
>
> I'm on HR and have noticed higher latencies (couple seconds 
> instead of e.g. 300ms) lately and sometimes higher error rates (a few 
> instead of 0-3). Yesterday over about 6 hours I got a ton of 
> 60-second 
> requests that threw 500's with accompanying messages [1], usually on 
> memcache sets hitting a deadline exceeded.  Also, over the last 
> couple 

[google-appengine] Re: More then 100 complains and no feedback from Google. Was: Outages?

[Rick Mangi]

They have responded. Look at the last comment in the thread before yours. 
I'm not trying to defend them by any means, I think the lack of response 
from google in general is quite disturbing, but Ikai did reply finally 
saying that they are working on it.

On Thursday, March 15, 2012 1:59:45 PM UTC-4, toonetown wrote:
>
> Yes - we are still seeing problems too - I think it is ridiculous that we 
> aren't hearing anything about the issue from Google...how they are planning 
> on addressing it, etc.
>
> There are over 15 bugs that are similar to 
> http://code.google.com/p/googleappengine/issues/detail?id=7133 - all have 
> been logged in the past 2 weeks, so that tells me that *SOMETHING* is 
> wrong...
>
> -Nathan
>
> On Wednesday, March 14, 2012 9:42:21 AM UTC-6, Mos wrote:
>>
>> Problem still exists: High latency and a significant number of requests 
>> fail or result in uncontrolled creation of new instances.
>>
>> GAE customers complain and complain for days.  It seems like many website 
>> have to accept that the 500-error is an integral feature of the GAE 
>> run-time.
>> Even worse:  The broken platform leads to increase usage of instances and 
>> therefore leads to higher costs for paying customer.
>>
>> No communication from Google; no feedback on the mailing list; no status 
>> updates on the issue tracker. 
>> Instead a always green status:   http://code.google.com/status/appengine 
>> (I think the GAE community needs to develop a crowed sources status page to 
>> get a picture what's really is going on)
>>
>> That makes me crazy.  I saw many platforms and business support forums 
>> the last years, but never encountered such an ignorance regarding custom 
>> complains. 
>>
>> The only official response I saw, was the "Escalated your issue to the 
>> reliability team" in one of the related issues:
>> http://code.google.com/p/googleappengine/issues/detail?id=7133 
>>
>> So, 'realiability team' what's going on? How is the status?
>>
>>
>>
>> On Tue, Mar 13, 2012 at 3:22 PM, Mos  wrote:
>>
>>> > What is your application id?
>>>
>>> krisen-talk(www.krisentalk.de)
>>>
>>>
>>> > Feel free to open a production issue
>>>
>>> There is already an issue from someone else (following this thread a lot 
>>> of people are affected):
>>>
>>> http://code.google.com/p/googleappengine/issues/detail?id=7133
>>>
>>> Johan, what's going on with GAE the last days?  It doesn't feel like a 
>>> PaaS in production mode.
>>> Perhaps Google should reintroduce the Beta status. ;)  
>>>
>>>
>>> On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine wrote:
>>>
 What is your application id?

 Feel free to open a production issue, if you want to investigate this 
 offthread:

 http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue


 On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:

> Same thing the last minutes on our app (HRD, Java, Low-Traffic, one 
> instance, no new deployment, simple page just hitting MemCache):
>
> "Request was aborted after waiting too long to attempt to service your 
> request."   -->  User sees 500er
>
> GAE-Team, what is going on the last days?  In my opinion the Google 
> App Engine is unreliable and looks more like a alpha- or beta- 
> cloudenvrionment
>
> Please Google share you analysis with us.
>
> Cheers
> Mos
>
>  
>
>  
>
> 2012/3/13 Sébastien Tromp 
>
>> Hello,
>>
>> Same thing here, since around an hour ago:
>> AppID: fiveorbsgame & fiveorbsgame-test
>>
>>
>> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov wrote:
>>
>>> I'm encountering the same issue with HR app. The spike got started 
>>> in about ~1 hour from now. 
>>>
>>> AppID: cmsevobg
>>> Datastore: HR
>>>
>>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:

 In case you're keeping track of issues thinking it's generally 
 cleared up:

 I'm on HR and have noticed higher latencies (couple seconds instead 
 of e.g. 300ms) lately and sometimes higher error rates (a few instead 
 of 
 0-3). Yesterday over about 6 hours I got a ton of 60-second requests 
 that 
 threw 500's with accompanying messages [1], usually on memcache sets 
 hitting a deadline exceeded.  Also, over the last couple weeks I've 
 been 
 running 3 instances permanently despite sometimes shutting them down 
 manually.  Usually I get by on one just fine with bursts of 2 or 3.  
 I've 
 noticed that one instance serves the majority of traffic with the 
 other two 
 serving maybe 50 requests over many hours, so the shutdown isn't 
 aggressive 
 enough.

 "This request caused a new process to be started for your 
 application..."
 +
 "A problem w

[google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[stevep]

Important also to know whether Scheduler makes decisions based on
average app latency or a more granular analysis of average latency per
specific call. Extending Tapir's example, if five new requests are
being queued that for calls that average less than 10 milliseconds,
Scheduler's spin-up decision might be different versus five requests
for a calls that average > 500 ms. --stevep

-- 
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: More then 100 complains and no feedback from Google. Was: Outages?

[toonetown]

Yes - we are still seeing problems too - I think it is ridiculous that we 
aren't hearing anything about the issue from Google...how they are planning 
on addressing it, etc.

There are over 15 bugs that are similar 
to http://code.google.com/p/googleappengine/issues/detail?id=7133 - all 
have been logged in the past 2 weeks, so that tells me that *SOMETHING* is 
wrong...

-Nathan

On Wednesday, March 14, 2012 9:42:21 AM UTC-6, Mos wrote:
>
> Problem still exists: High latency and a significant number of requests 
> fail or result in uncontrolled creation of new instances.
>
> GAE customers complain and complain for days.  It seems like many website 
> have to accept that the 500-error is an integral feature of the GAE 
> run-time.
> Even worse:  The broken platform leads to increase usage of instances and 
> therefore leads to higher costs for paying customer.
>
> No communication from Google; no feedback on the mailing list; no status 
> updates on the issue tracker. 
> Instead a always green status:   http://code.google.com/status/appengine 
> (I think the GAE community needs to develop a crowed sources status page to 
> get a picture what's really is going on)
>
> That makes me crazy.  I saw many platforms and business support forums the 
> last years, but never encountered such an ignorance regarding custom 
> complains. 
>
> The only official response I saw, was the "Escalated your issue to the 
> reliability team" in one of the related issues:
> http://code.google.com/p/googleappengine/issues/detail?id=7133 
>
> So, 'realiability team' what's going on? How is the status?
>
>
>
> On Tue, Mar 13, 2012 at 3:22 PM, Mos  wrote:
>
>> > What is your application id?
>>
>> krisen-talk(www.krisentalk.de)
>>
>>
>> > Feel free to open a production issue
>>
>> There is already an issue from someone else (following this thread a lot 
>> of people are affected):
>>
>> http://code.google.com/p/googleappengine/issues/detail?id=7133
>>
>> Johan, what's going on with GAE the last days?  It doesn't feel like a 
>> PaaS in production mode.
>> Perhaps Google should reintroduce the Beta status. ;)  
>>
>>
>> On Tue, Mar 13, 2012 at 3:10 PM, Johan Euphrosine wrote:
>>
>>> What is your application id?
>>>
>>> Feel free to open a production issue, if you want to investigate this 
>>> offthread:
>>>
>>> http://code.google.com/p/googleappengine/issues/entry?template=Production%20issue
>>>
>>>
>>> On Tue, Mar 13, 2012 at 11:44 AM, Mos  wrote:
>>>
 Same thing the last minutes on our app (HRD, Java, Low-Traffic, one 
 instance, no new deployment, simple page just hitting MemCache):

 "Request was aborted after waiting too long to attempt to service your 
 request."   -->  User sees 500er

 GAE-Team, what is going on the last days?  In my opinion the Google App 
 Engine is unreliable and looks more like a alpha- or beta- 
 cloudenvrionment

 Please Google share you analysis with us.

 Cheers
 Mos

  

  

 2012/3/13 Sébastien Tromp 

> Hello,
>
> Same thing here, since around an hour ago:
> AppID: fiveorbsgame & fiveorbsgame-test
>
>
> On Tue, Mar 13, 2012 at 9:59 AM, Miroslav Genov wrote:
>
>> I'm encountering the same issue with HR app. The spike got started in 
>> about ~1 hour from now. 
>>
>> AppID: cmsevobg
>> Datastore: HR
>>
>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>>
>>> In case you're keeping track of issues thinking it's generally 
>>> cleared up:
>>>
>>> I'm on HR and have noticed higher latencies (couple seconds instead 
>>> of e.g. 300ms) lately and sometimes higher error rates (a few instead 
>>> of 
>>> 0-3). Yesterday over about 6 hours I got a ton of 60-second requests 
>>> that 
>>> threw 500's with accompanying messages [1], usually on memcache sets 
>>> hitting a deadline exceeded.  Also, over the last couple weeks I've 
>>> been 
>>> running 3 instances permanently despite sometimes shutting them down 
>>> manually.  Usually I get by on one just fine with bursts of 2 or 3.  
>>> I've 
>>> noticed that one instance serves the majority of traffic with the other 
>>> two 
>>> serving maybe 50 requests over many hours, so the shutdown isn't 
>>> aggressive 
>>> enough.
>>>
>>> "This request caused a new process to be started for your 
>>> application..."
>>> +
>>> "A problem was encountered with the process that handled this 
>>> request, causing it to exit" in the same request.
>>>
>>> App-id: 2dumo-hr
>>>
>>
>> On Tuesday, March 13, 2012 10:36:38 AM UTC+2, Richard Watson wrote:
>>>
>>> In case you're keeping track of issues thinking it's generally 
>>> cleared up:
>>>
>>> I'm on HR and have noticed higher latencies (couple seconds instead 
>>> of e.g. 300ms) lately and sometimes hig

[google-appengine] Re: 500 errors + high latency + please communicate with us

[toonetown]

You can see the full list of bugs in this 
thread: 
https://groups.google.com/d/topic/google-appengine/nNoWv1uVqwo/discussion

-Nathan

On Thursday, March 15, 2012 11:48:17 AM UTC-6, toonetown wrote:
>
> Same here - please see 
> http://code.google.com/p/googleappengine/issues/detail?id=7133 for some 
> more details (there are at least 15 other bugs logged with the same 
> issue...we need to make this issue more visible to Google...)
>
> -Nathan
>
> On Sunday, March 11, 2012 1:05:45 PM UTC-6, Rafael Gutierrez wrote:
>>
>> We are having the same issue (DeadlineExceptions, 
>> InitializationExceptions, etc) since the last maintenance.
>>
>> More than that, we have some remote units that make HTTP requests to post 
>> data to our application using an GPRS module.
>> Some of those units (more than 40) are no longer sending these requests 
>> (we can't even see them in the logs), meanwhile NOTHING changed in the 
>> remote units code (stable for over 1 year), and we verified that they still 
>> connecting to the GPRS carrier.
>>
>> Please Google, give me some feedback... our clients are pushing us to 
>> have some news, and we can't even justify them the technical issues. It 
>> could kill our business reliability and reputation. 
>>
>> App Id: innervision-ui :: Master/Slave
>>
>

-- 
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/-/o5gWsch5FVsJ.
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: 500 errors + high latency + please communicate with us

[toonetown]

Same here - please 
see http://code.google.com/p/googleappengine/issues/detail?id=7133 for some 
more details (there are at least 15 other bugs logged with the same 
issue...we need to make this issue more visible to Google...)

-Nathan

On Sunday, March 11, 2012 1:05:45 PM UTC-6, Rafael Gutierrez wrote:
>
> We are having the same issue (DeadlineExceptions, 
> InitializationExceptions, etc) since the last maintenance.
>
> More than that, we have some remote units that make HTTP requests to post 
> data to our application using an GPRS module.
> Some of those units (more than 40) are no longer sending these requests 
> (we can't even see them in the logs), meanwhile NOTHING changed in the 
> remote units code (stable for over 1 year), and we verified that they still 
> connecting to the GPRS carrier.
>
> Please Google, give me some feedback... our clients are pushing us to have 
> some news, and we can't even justify them the technical issues. It could 
> kill our business reliability and reputation. 
>
> App Id: innervision-ui :: Master/Slave
>

-- 
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/-/cwwokSPIf94J.
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 latency since March 13th

[toonetown]

Looks like this is a big issue - there is another thread about it at
http://groups.google.com/group/google-appengine/browse_thread/thread/baf6af00b0a46709

I can also verify that this is happening to us.  In looking through
the issue list, it appears that *SOMETHING* happened a couple weeks
ago, causing all sorts of people to have Deadline and HardDeadline
exceptions.  In addition, since so many instances are starting and
stopping, it appears that performance has been hampered as well.
Also - in looking through the issue list, it seems that this is
mostly
affecting Java AppEngine instances - but similar problems appear to
be
happening in the Python instances as well.

>From what I can tell in reading forums and postings, there was a
system update at some point on March 7th, 2012, and problems have
been
happening ever since.

Here is a list (from a quick scan - may not be comprehensive) of all
the bugs I have found that are having this issue:
http://code.google.com/p/googleappengine/issues/detail?id=7133
http://code.google.com/p/googleappengine/issues/detail?id=7130
http://code.google.com/p/googleappengine/issues/detail?id=7135
http://code.google.com/p/googleappengine/issues/detail?id=7138
http://code.google.com/p/googleappengine/issues/detail?id=7143
http://code.google.com/p/googleappengine/issues/detail?id=7146
http://code.google.com/p/googleappengine/issues/detail?id=7153
http://code.google.com/p/googleappengine/issues/detail?id=7093
http://code.google.com/p/googleappengine/issues/detail?id=7097
http://code.google.com/p/googleappengine/issues/detail?id=7101
http://code.google.com/p/googleappengine/issues/detail?id=7102
http://code.google.com/p/googleappengine/issues/detail?id=7103
http://code.google.com/p/googleappengine/issues/detail?id=7108
http://code.google.com/p/googleappengine/issues/detail?id=7113
http://code.google.com/p/googleappengine/issues/detail?id=7121
http://code.google.com/p/googleappengine/issues/detail?id=7122

I would suggest that we all vote for a single one of these - so that
it get get some visibility within Google.  I think we should vote for
http://code.google.com/p/googleappengine/issues/detail?id=7133 since
as of today, it has the most stars already, and it is listed as
status
"Accepted" - which is better than all the other ones that are listed
as "New".

We are paying for AppEngine, we expect that there should be some
level
of support.  This is ridiculous to have this problem going
on for as long as it has been, with no word on what is going on or
how
to resolve it.

(Yes - this is a cross-post...but *something* needs to be done to have
the visibility of this issue raised)

-Nathan

On Mar 15, 11:05 am, Thomas  wrote:
> Hi Ikai,
>
> I've been writing in similar threads for about a week. Our app
> (id=typescout) lately experienced very high latency but was somehow
> performing better since Monday. Today again, performance broke down, and we
> see lots of requests taking over 50s or failing without any reason.
> I can remember, more than half a year ago appengine "stability" often was
> as bad as it was the last two weeks, but everything worked beautifully
> since then. Unfortunately, during the last two weeks, appengine performance
> was really horrible for us and our users.
> Do you think this problems will be resolved by the scheduled maintenance on
> Monday 19th? We're using M/S, because we sometimes have lots of concurrent
> writes which would just not work well with HRD. At the same time, we tried
> to run our app with HRD and read/write quota was running up incredibly
> fast, about 10-50 times faster than M/S, so we decided not to migrate our
> app.
>
> Thanks for your support!
>
> Kind regards,
> Thomas
>
> Am Donnerstag, 15. März 2012 16:31:53 UTC+1 schrieb Ikai Lan:
>
>
>
>
>
>
>
>
>
> > I see. Let's continue watching this to look for trends. Please post if it
> > fluctuates either higher or lower.
>
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Engine
> > plus.ikailan.com
>
> > On Thu, Mar 15, 2012 at 4:19 AM, andidol wrote:
>
> >> I'm doing a Model.get_by_key_name().. on a model with ~50 million entries
> >> (I know this should not effect the query-time). The Model.get_by_key_name()
> >> method often takes more than 200ms for finding an entry, not every time but
> >> often. Not finding a key fails much faster, IMO this is ok. I think this is
> >> not normal, do you have any suggestions?
>
> >> On Wednesday, March 14, 2012 8:01:26 PM UTC+1, Ikai Lan wrote:
>
> >>> We're addressing issues with high replication datastore applications.
>
> >>> In the future, however, this information is typically not enough. What
> >>> are you doing? Are you making datastore calls? Are you doing URLFetch? Are
> >>> you making XMPP or email API calls? Are CPU intensive tasks slower? This 
> >>> is
> >>> important because there are a lot of operat

[google-appengine] Re: Lots of HTTP 500 errors and all instances restarted by GAE!

[toonetown]

I can also verify that this is happening to us.  In looking through
the issue list, it appears that *SOMETHING* happened a couple weeks
ago, causing all sorts of people to have Deadline and HardDeadline
exceptions.  In addition, since so many instances are starting and
stopping, it appears that performance has been hampered as well.

Also - in looking through the issue list, it seems that this is mostly
affecting Java AppEngine instances - but similar problems appear to be
happening in the Python instances as well.

>From what I can tell in reading forums and postings, there was a
system update at some point on March 7th, 2012, and problems have been
happening ever since.

Here is a list (from a quick scan - may not be comprehensive) of all
the bugs I have found that are having this issue:
http://code.google.com/p/googleappengine/issues/detail?id=7133
http://code.google.com/p/googleappengine/issues/detail?id=7130
http://code.google.com/p/googleappengine/issues/detail?id=7135
http://code.google.com/p/googleappengine/issues/detail?id=7138
http://code.google.com/p/googleappengine/issues/detail?id=7143
http://code.google.com/p/googleappengine/issues/detail?id=7146
http://code.google.com/p/googleappengine/issues/detail?id=7153
http://code.google.com/p/googleappengine/issues/detail?id=7093
http://code.google.com/p/googleappengine/issues/detail?id=7097
http://code.google.com/p/googleappengine/issues/detail?id=7101
http://code.google.com/p/googleappengine/issues/detail?id=7102
http://code.google.com/p/googleappengine/issues/detail?id=7103
http://code.google.com/p/googleappengine/issues/detail?id=7108
http://code.google.com/p/googleappengine/issues/detail?id=7113
http://code.google.com/p/googleappengine/issues/detail?id=7121
http://code.google.com/p/googleappengine/issues/detail?id=7122

I would suggest that we all vote for a single one of these - so that
it get get some visibility within Google.  I think we should vote for
http://code.google.com/p/googleappengine/issues/detail?id=7133 since
as of today, it has the most stars already, and it is listed as status
"Accepted" - which is better than all the other ones that are listed
as "New".

We are paying for AppEngine, we expect that there should be some level
of support.  This is ridiculous to have this problem going
on for as long as it has been, with no word on what is going on or how
to resolve it.

-Nathan

On Mar 13, 4:35 pm, Mos  wrote:
> Vote for the 
> issue:http://code.google.com/p/googleappengine/issues/detail?id=7133
>
> I hope Google will give some feedback soon ?!
>
> On Tue, Mar 13, 2012 at 5:41 PM, Nicanor Babula 
> wrote:
>
>
>
>
>
>
>
> > Same thing here too!
>
> > appid: domodentweb2
> > datastore: HRD
>
> > Getting calls and emails from angry customers.
> > Please, help!
> > Thanks.
>
> > On Tue, Mar 13, 2012 at 5:38 PM, Mark  wrote:
>
> >> This is happening to me too.  Instances getting restarted, and requests
> >> taking way longer than usual.  Getting emails from unhappy users.
>
> >> My app id is bedbuzzserver, on HR ( & Java)
>
> >> --
> >> 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/-/gX9u1do57t0J.
>
> >> 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.
>
> > --
> > Nicanor Cristian Babula
>
> >  --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.

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

Re: [google-appengine] Very high latency since March 13th

[Thomas]

Hi Ikai,

I've been writing in similar threads for about a week. Our app 
(id=typescout) lately experienced very high latency but was somehow 
performing better since Monday. Today again, performance broke down, and we 
see lots of requests taking over 50s or failing without any reason. 
I can remember, more than half a year ago appengine "stability" often was 
as bad as it was the last two weeks, but everything worked beautifully 
since then. Unfortunately, during the last two weeks, appengine performance 
was really horrible for us and our users.
Do you think this problems will be resolved by the scheduled maintenance on 
Monday 19th? We're using M/S, because we sometimes have lots of concurrent 
writes which would just not work well with HRD. At the same time, we tried 
to run our app with HRD and read/write quota was running up incredibly 
fast, about 10-50 times faster than M/S, so we decided not to migrate our 
app.

Thanks for your support!

Kind regards,
Thomas


Am Donnerstag, 15. März 2012 16:31:53 UTC+1 schrieb Ikai Lan:
>
> I see. Let's continue watching this to look for trends. Please post if it 
> fluctuates either higher or lower.
>
> --
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
> On Thu, Mar 15, 2012 at 4:19 AM, andidol wrote:
>
>> I'm doing a Model.get_by_key_name().. on a model with ~50 million entries 
>> (I know this should not effect the query-time). The Model.get_by_key_name() 
>> method often takes more than 200ms for finding an entry, not every time but 
>> often. Not finding a key fails much faster, IMO this is ok. I think this is 
>> not normal, do you have any suggestions?
>>
>>
>> On Wednesday, March 14, 2012 8:01:26 PM UTC+1, Ikai Lan wrote:
>>>
>>> We're addressing issues with high replication datastore applications. 
>>>
>>> In the future, however, this information is typically not enough. What 
>>> are you doing? Are you making datastore calls? Are you doing URLFetch? Are 
>>> you making XMPP or email API calls? Are CPU intensive tasks slower? This is 
>>> important because there are a lot of operations for which 200ms would seem 
>>> low latency. If you're trying to brute force SHA1 hashes and it's taking 
>>> 500ms on average, you're doing okay.
>>>
>>> One of the fortunate things about working with software developers 
>>> instead of normal internet consumers is that I can usually just give the 
>>> guidance, "report issues that way you want your users to report issues or 
>>> bugs", and it gets the message across =).
>>>
>>> --
>>> Ikai Lan 
>>> Developer Programs Engineer, Google App Engine
>>> plus.ikailan.com
>>>
>>>
>>>
>>> On Wed, Mar 14, 2012 at 5:48 AM, andidol wrote:
>>>
 Hi,

 I have very high latency on my AppEngine since yesterday. It was really 
 fast before < 100ms. Now there are a lot of requests performing with > 
 200ms without any reason. I did not update or did anything.
 I'm using High Replication Datastore.

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

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

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

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Prashant Hegde]

Almost identical setup and observations. 

In addition,

We are observing that one instance with very few warmups (spin offs of new 
instances) can be achieved with min instances = auto and max = 1. Our traffic 
is not that much ~ 1 QPS with mostly < 1 s latency


Thanks
Prashant


On 15-Mar-2012, at 8:53 PM, Jeff Schnitzer wrote:

> That is not quite the behavior I observe.  It largely looks like this:
> 
> - I1 is warm and ready
> - the request comes in
> - the request goes to I2 and blocks while it starts up
> - another request comes, goes to I3 and blocks while it starts up
> 
> While it's not 100%, GAE seems to route a disturbing number of
> requests (say, 1 out of 10)  to not-warmed-up instances.  Just
> clicking around the site produces large numbers of UX delays while an
> instance starts.  The dashboard often shows three instances.  This is
> in java with threadsafe-true and F1 instances and not particularly
> CPU-intensive operations; my requests do a lot of data operations and
> almost all have <1s latency.
> 
> This is with the setting at 1 min idle, 1 max idle.  I've disabled
> billing on my sandbox app so I can't experiment anymore - I'm not
> willing to try this experiment on production.  I was still seeing this
> behavior a week ago.  Switching to Auto/Auto, I almost never see more
> than one instance and startup requests are nearly absent from the
> logs.
> 
> I understand that min idle instances tries to keep them idle in
> reserve.  The problem is that the reserve doesn't seem to get used.  I
> can't think of any rationale for routing a user request to an instance
> startup while there is idle capacity just sitting by.  Or even if it
> isn't idle that second, it will be in short order - waiting 1s is
> better than waiting 20s for a whole instance.
> 
> Jeff
> 
> On Thu, Mar 15, 2012 at 3:54 AM, Gregory D'alesandre  wrote:
>> Hey Jeff,
>> 
>> The way it is supposed to work with min idle instances set is:
>> - idle instance is warm and ready (let's call it I1)
>> - request comes in
>> - request goes to the idle instance at which point another instance is
>> immediately spun up (let's call it I2)
>> - you now have 1 idle instance (I2) as well as 1 instance serving traffic
>> (I1)
>> 
>> I know it might seem like we are taking the label too literally but we are
>> trying to maintain idle capacity for you.  The tricky part is since we
>> always spin up a new idle instance when an existing one begins to serve
>> traffic it looks like they are sitting around unused when they are in fact
>> being used often just others immediately take their place.  Are you sure
>> this is not the behavior your are observing?
>> 
>> Thanks,
>> 
>> Greg
>> 
>> On Wed, Mar 14, 2012 at 8:00 AM, Jeff Schnitzer  wrote:
>>> 
>>> On Wed, Mar 14, 2012 at 4:28 AM, Tapir  wrote:
 
 On Mar 14, 1:17 pm, Gopal Patel  wrote:
> you mean, always have one instance more than required ? ( who is going
> to
> pay for that ? ) , and is not minimum idle instance same thing ?
 
 It is different with the normal resident instance.
 It is an instance to handle requests only at the time of the situation
 "no available instances and need create a new instance",
 so that many "Cold Starts" can be avoided.
>>> 
>>> This is pretty much exactly what setting minimum idle instances does.
>>> Requests are preferentially routed to dynamic instances rather than
>>> resident instances.
>>> 
>>> The problem is, something in the scheduler is broken.  Instead of
>>> routing requests to the idle instance, GAE prefers to route requests
>>> to a fresh instance, causing the user to wait while an instance warms
>>> up.  That setting is probably best described as "minimum useless
>>> instances".  Maybe somebody took the "minimum _idle_ instances" label
>>> too literally ;-)
>>> 
>>> This is the behavior I observed a week or two ago.  Hopefully it will
>>> be fixed.  Doesn't sound like it has been so far.
>>> 
>>> Jeff
>>> 
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Google App Engine" group.
>>> To post to this group, send email to google-appengine@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> google-appengine+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/google-appengine?hl=en.
>>> 
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
> 
> -- 
> 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, sen

Re: [google-appengine] Storing from PDF to IMG

[Max]

Where is the file api?
Sorry, I can't understand what you refer to. Could you please push me in 
the right direction?

Il giorno giovedì 15 marzo 2012 16:34:51 UTC+1, Jeff Schnitzer ha scritto:
>
> You must use the Files API to write the generated image to the blobstore.
>
> Jeff
>
> On Thu, Mar 15, 2012 at 6:16 AM, Max  
> wrote:
> > Dear All,
> > I'm always storing the img I receive in the blobstore using this code:
> >
> > class UploadHandler(blobstore_handlers.BlobstoreUploadHandler):
> >  def post(self):
> >  upload_files = self.get_uploads('File')
> >  blob_info = upload_files[0]
> >  fotos = FOTO()
> >  fotos.link = blob_info.key()
> >  fotos.Tlink = images.get_serving_url(fotos.link, 94)
> >  fotos.Glink = images.get_serving_url(fotos.link, 800)
> >  fotos.put()
> >
> > Now I receive a PDF and I have to store an IMG.
> > And I'm thinking to use the conversions tool as per below.
> >
> > from google.appengine.api import conversion
> >
> > # Create a conversion request from HTML to PNG.
> > asset = conversion.Asset("text/html", "some data", "test.html")
> > conversion_obj = conversion.Conversion(asset, "image/png")
> >
> > result = conversion.convert(conversion_obj)
> > if result.assets:
> >   # Note: in most cases, we will return data all in one asset.
> >   # Except that we return multiple assets for multiple pages image.
> >   for asset in result.assets:
> > doSomethingWithAsset(asset.data)
> > else:
> >   handleError(result.error_code, result.error_text)
> >
> >
> > My question is:
> > How can I store the asset? Could I still use the way I was?
> >
> > Thanks
> >
> > Max
> >
> > --
> > 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/-/BDSZMmVUHJAJ.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> > http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/l0Ru5iODU38J.
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: using GAE with javascript

[that an]

Thanks - I appreciate the candor and insight.

On Mar 14, 8:27 pm, "Ikai Lan (Google)"  wrote:
> For raw access, pretty much the barrier is demand. There's some argument
> for raw datastore access via Javascript, but then there are all kinds of
> messy business logic and security that you'd have to specify anyway.
>
> Unless you are just talking about using HTML5 and Javascript to talk to
> Python/Java/Go. You can do that today. But odds are good you don't want to
> give unfettered access to every single user of your application. That's why
> you write the Python/Java/Go code: to implement the business logic.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
>
>
>
>
> On Wed, Mar 14, 2012 at 7:03 PM, that an  wrote:
> > Thanks for the link.  I really appreciate the response straight from
> > the source.  And it helps confirm for me that I'm probably looking for
> > something that doesn't yet exist.
>
> > But what is the barrier for Google providing access to GAE via
> > javascript?
>
> > GWT is, after all, converted to javascript when it is running on the
> > client - so it is technically possible.  And communication between
> > client and server, no matter what platform they use is standard HTTP
> > protocol - neither client or server really cares (or should care)
> > about how the other is implemented.
>
> > I'm not trying to be obtuse, but it just seems like such a...
> > natural... fit and obvious gap in the simplicity of the development.
> > Write your GAE server in a natural server side language like Python or
> > Java, and write your client in a natural client side language like
> > javascript and HTML5.
>
> > Is there a reason that I've missed?  Help me out here - I just don't
> > understand the omission...
>
> > On Mar 14, 1:40 pm, "Ikai Lan (Google)"  wrote:
> > > I wouldn't say dancing - we just don't provide that kind of access. Even
> > if
> > > we ever did in the future, we would likely wrap an auth layer around it
> > > (probably OAuth 2.0).
>
> > > This might be the closest thing you are looking for:
>
> > >http://code.google.com/p/google-protorpc/
>
> > > But I don't have any thoughts about security, and you'd have to write the
> > > code yourself to translate requests to datastore calls.
>
> > > --
> > > Ikai Lan
> > > Developer Programs Engineer, Google App Engine
> > > plus.ikailan.com
>
> > > On Mon, Mar 12, 2012 at 8:31 PM, that an  wrote:
> > > > I'm looking for a way to use javascript code to directly interface
> > > > with the google app engine and with the datastore.
>
> > > > I've already used the GWT/GAE Java SDK in Eclipse with varying levels
> > > > of success, but I'm looking for a way to leverage the benefits of GAE
> > > > cloud services with the direct DOM manipulation of writing javascript
> > > > directly for the client.  GWT front end just doesn't seem flexible
> > > > enough to do what javascript can.
>
> > > > Maybe I've missed something obvious, or something that is out there
> > > > does it, but I've been searching for awhile now, and it just seems
> > > > like Google is dancing around any direct client access to their App
> > > > Engine and cloud datastore.
>
> > > > I've pretty much exhausted my leads so far - Any direction is greatly
> > > > appreciated.
>
> > > > --
> > > > 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.

Re: [google-appengine] Storing from PDF to IMG

[Jeff Schnitzer]

You must use the Files API to write the generated image to the blobstore.

Jeff

On Thu, Mar 15, 2012 at 6:16 AM, Max  wrote:
> Dear All,
> I'm always storing the img I receive in the blobstore using this code:
>
> class UploadHandler(blobstore_handlers.BlobstoreUploadHandler):
>  def post(self):
>  upload_files = self.get_uploads('File')
>  blob_info = upload_files[0]
>  fotos = FOTO()
>  fotos.link = blob_info.key()
>  fotos.Tlink = images.get_serving_url(fotos.link, 94)
>  fotos.Glink = images.get_serving_url(fotos.link, 800)
>  fotos.put()
>
> Now I receive a PDF and I have to store an IMG.
> And I'm thinking to use the conversions tool as per below.
>
> from google.appengine.api import conversion
>
> # Create a conversion request from HTML to PNG.
> asset = conversion.Asset("text/html", "some data", "test.html")
> conversion_obj = conversion.Conversion(asset, "image/png")
>
> result = conversion.convert(conversion_obj)
> if result.assets:
>   # Note: in most cases, we will return data all in one asset.
>   # Except that we return multiple assets for multiple pages image.
>   for asset in result.assets:
>     doSomethingWithAsset(asset.data)
> else:
>   handleError(result.error_code, result.error_text)
>
>
> My question is:
> How can I store the asset? Could I still use the way I was?
>
> Thanks
>
> Max
>
> --
> 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/-/BDSZMmVUHJAJ.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

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

Re: [google-appengine] Very high latency since March 13th

[Ikai Lan (Google)]

I see. Let's continue watching this to look for trends. Please post if it
fluctuates either higher or lower.

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Thu, Mar 15, 2012 at 4:19 AM, andidol  wrote:

> I'm doing a Model.get_by_key_name().. on a model with ~50 million entries
> (I know this should not effect the query-time). The Model.get_by_key_name()
> method often takes more than 200ms for finding an entry, not every time but
> often. Not finding a key fails much faster, IMO this is ok. I think this is
> not normal, do you have any suggestions?
>
>
> On Wednesday, March 14, 2012 8:01:26 PM UTC+1, Ikai Lan wrote:
>>
>> We're addressing issues with high replication datastore applications.
>>
>> In the future, however, this information is typically not enough. What
>> are you doing? Are you making datastore calls? Are you doing URLFetch? Are
>> you making XMPP or email API calls? Are CPU intensive tasks slower? This is
>> important because there are a lot of operations for which 200ms would seem
>> low latency. If you're trying to brute force SHA1 hashes and it's taking
>> 500ms on average, you're doing okay.
>>
>> One of the fortunate things about working with software developers
>> instead of normal internet consumers is that I can usually just give the
>> guidance, "report issues that way you want your users to report issues or
>> bugs", and it gets the message across =).
>>
>> --
>> Ikai Lan
>> Developer Programs Engineer, Google App Engine
>> plus.ikailan.com
>>
>>
>>
>> On Wed, Mar 14, 2012 at 5:48 AM, andidol wrote:
>>
>>> Hi,
>>>
>>> I have very high latency on my AppEngine since yesterday. It was really
>>> fast before < 100ms. Now there are a lot of requests performing with >
>>> 200ms without any reason. I did not update or did anything.
>>> I'm using High Replication Datastore.
>>>
>>> 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/-/**UKDaOm5bNJsJ
>>> .
>>> To post to this group, send email to 
>>> google-appengine@googlegroups.**com
>>> .
>>> To unsubscribe from this group, send email to
>>> google-appengine+unsubscribe@**googlegroups.com
>>> .
>>> For more options, visit this group at http://groups.google.com/**
>>> group/google-appengine?hl=en
>>> .
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/_OFHy-k7QE8J.
>
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>

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

Re: [google-appengine] Re: timed out on datastore operations!

[Ikai Lan (Google)]

Deployment issues are generally independent of datastore issues. Are you
running on high replication datastore or master/slave datastore?

--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com



On Thu, Mar 15, 2012 at 10:54 AM, Tom Davis  wrote:

> Yes, I have applications that simply timeout on all Datastore operations
> (DeadlineExceededError after 60 seconds), regardless of type or data
> characteristics.
>
> On Thu, 15 Mar 2012 15:40:11 +0530, Sandeep Koduri wrote:
> > even deployment fails..
> > Cloned 100 files.
> > Cloned 200 files.
> > Cloned 300 files.
> > Cloned 400 files.
> > Cloned 500 files.
> > Cloned 600 files.
> > Cloning 414 application files.
> > Rolling back the update.
> > Error 500: --- begin server output ---
> >
> > 
> > 
> > 500 Server Error
> > 
> > 
> > Error: Server Error
> > The server encountered an error and could not complete your
> > request.If th
> > e problem persists, please http://code.google.com/appengine/community.h
> > tml">report your problem and mention this error message and the query
> > that c
> > aused it.
> > 
> > 
> >
> > On Thu, Mar 15, 2012 at 3:22 PM, Sandeep Koduri <
> sandeep.kod...@gmail.com>wrote:
> >
> > > Hi,
> > >
> > > Any one facing same issues
> > >
> > >
> > >
> http://code.google.com/status/appengine/detail/datastore/2012/03/15#ae-trust-detail-datastore-get-latency
> > >
> > >
> > > Or any thing on my ID?[?][?][?]
> > >
> > > --
> > > Regards
> > > Sandeep Koduri
> > > Phone: +91- 99 666 02 456
> > > Gtalk: sandeep.koduri | Skype: sandeep.koduri
> > > P Please consider the environment before printing this email
> > >
> > >
> >
> >
> > --
> > Regards
> > Sandeep Koduri
> > Phone: +91- 99 666 02 456
> > Gtalk: sandeep.koduri | Skype: sandeep.koduri
> > P Please consider the environment before printing this email
> >
> > --
> > 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.

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Jeff Schnitzer]

That is not quite the behavior I observe.  It largely looks like this:

 - I1 is warm and ready
 - the request comes in
 - the request goes to I2 and blocks while it starts up
 - another request comes, goes to I3 and blocks while it starts up

While it's not 100%, GAE seems to route a disturbing number of
requests (say, 1 out of 10)  to not-warmed-up instances.  Just
clicking around the site produces large numbers of UX delays while an
instance starts.  The dashboard often shows three instances.  This is
in java with threadsafe-true and F1 instances and not particularly
CPU-intensive operations; my requests do a lot of data operations and
almost all have <1s latency.

This is with the setting at 1 min idle, 1 max idle.  I've disabled
billing on my sandbox app so I can't experiment anymore - I'm not
willing to try this experiment on production.  I was still seeing this
behavior a week ago.  Switching to Auto/Auto, I almost never see more
than one instance and startup requests are nearly absent from the
logs.

I understand that min idle instances tries to keep them idle in
reserve.  The problem is that the reserve doesn't seem to get used.  I
can't think of any rationale for routing a user request to an instance
startup while there is idle capacity just sitting by.  Or even if it
isn't idle that second, it will be in short order - waiting 1s is
better than waiting 20s for a whole instance.

Jeff

On Thu, Mar 15, 2012 at 3:54 AM, Gregory D'alesandre  wrote:
> Hey Jeff,
>
> The way it is supposed to work with min idle instances set is:
> - idle instance is warm and ready (let's call it I1)
> - request comes in
> - request goes to the idle instance at which point another instance is
> immediately spun up (let's call it I2)
> - you now have 1 idle instance (I2) as well as 1 instance serving traffic
> (I1)
>
> I know it might seem like we are taking the label too literally but we are
> trying to maintain idle capacity for you.  The tricky part is since we
> always spin up a new idle instance when an existing one begins to serve
> traffic it looks like they are sitting around unused when they are in fact
> being used often just others immediately take their place.  Are you sure
> this is not the behavior your are observing?
>
> Thanks,
>
> Greg
>
> On Wed, Mar 14, 2012 at 8:00 AM, Jeff Schnitzer  wrote:
>>
>> On Wed, Mar 14, 2012 at 4:28 AM, Tapir  wrote:
>> >
>> > On Mar 14, 1:17 pm, Gopal Patel  wrote:
>> >> you mean, always have one instance more than required ? ( who is going
>> >> to
>> >> pay for that ? ) , and is not minimum idle instance same thing ?
>> >
>> > It is different with the normal resident instance.
>> > It is an instance to handle requests only at the time of the situation
>> > "no available instances and need create a new instance",
>> > so that many "Cold Starts" can be avoided.
>>
>> This is pretty much exactly what setting minimum idle instances does.
>> Requests are preferentially routed to dynamic instances rather than
>> resident instances.
>>
>> The problem is, something in the scheduler is broken.  Instead of
>> routing requests to the idle instance, GAE prefers to route requests
>> to a fresh instance, causing the user to wait while an instance warms
>> up.  That setting is probably best described as "minimum useless
>> instances".  Maybe somebody took the "minimum _idle_ instances" label
>> too literally ;-)
>>
>> This is the behavior I observed a week or two ago.  Hopefully it will
>> be fixed.  Doesn't sound like it has been so far.
>>
>> Jeff
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

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

Re: [google-appengine] Re: using GAE with javascript

[Jeff Schnitzer]

On Wed, Mar 14, 2012 at 10:03 PM, that an  wrote:
>
> But what is the barrier for Google providing access to GAE via
> javascript?

The only place where this would have any utility would be in a
contained 100% trusted environment where every user can be assumed to
be an administrator of everything.  This is not a common scenario...
and furthermore, most times where this scenario is assumed, it is a
mistake.

Jeff

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

Re: [google-appengine] Re: timed out on datastore operations!

[Tom Davis]

Yes, I have applications that simply timeout on all Datastore operations
(DeadlineExceededError after 60 seconds), regardless of type or data
characteristics.

On Thu, 15 Mar 2012 15:40:11 +0530, Sandeep Koduri wrote:
> even deployment fails..
> Cloned 100 files.
> Cloned 200 files.
> Cloned 300 files.
> Cloned 400 files.
> Cloned 500 files.
> Cloned 600 files.
> Cloning 414 application files.
> Rolling back the update.
> Error 500: --- begin server output ---
> 
> 
> 
> 500 Server Error
> 
> 
> Error: Server Error
> The server encountered an error and could not complete your
> request.If th
> e problem persists, please http://code.google.com/appengine/community.h
> tml">report your problem and mention this error message and the query
> that c
> aused it.
> 
> 
> 
> On Thu, Mar 15, 2012 at 3:22 PM, Sandeep Koduri 
> wrote:
> 
> > Hi,
> >
> > Any one facing same issues
> >
> >
> > http://code.google.com/status/appengine/detail/datastore/2012/03/15#ae-trust-detail-datastore-get-latency
> >
> >
> > Or any thing on my ID?[?][?][?]
> >
> > --
> > Regards
> > Sandeep Koduri
> > Phone: +91- 99 666 02 456
> > Gtalk: sandeep.koduri | Skype: sandeep.koduri
> > P Please consider the environment before printing this email
> >
> >
> 
> 
> -- 
> Regards
> Sandeep Koduri
> Phone: +91- 99 666 02 456
> Gtalk: sandeep.koduri | Skype: sandeep.koduri
> P Please consider the environment before printing this email
> 
> -- 
> 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: Javaland scheduler behavior

[Jason Collins]

Mauricio,

We opened an Enterprise support ticket on the topic and were told that
in order to get warmup requests, you have to have at least one min
idle instances. I believe this change occurred around 1.6.2.

Unfortunately, I can't get you the exact quotes from the support
person because, ironically, the Enterprise support system is down at
the moment.

j

On Mar 15, 1:37 am, Mauricio Aristizabal  wrote:
> Jason, how do you know you must have a resident instance to get warmup
> requests to work?  I don't see this anywhere in the docs. And to enable one
> do I just define a backend in backends.xml?
>
> I'm pretty sure warmups were working for me before but haven't seen them
> happening in the logs for a while now. I don't know if I did anything on my
> end but I've been trying to turn them on and nothing I do works.
>

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

Re: [google-appengine] Deploy fails

[Nicanor Babula]

I retried after awhile and it worked. Who knows...

On Thu, Mar 15, 2012 at 3:08 PM, Andrin von Rechenberg
wrote:

> It's extremely slow for me too
> appid: miumeet-hr
>
>
> On Thu, Mar 15, 2012 at 11:11 AM, Nicanor Babula  > wrote:
>
>> I wouldn't want to be in the appengine team right now... ;) Hope they'll
>> fix this soon.
>>
>>
>> On Thu, Mar 15, 2012 at 11:09 AM, Sandeep Koduri <
>> sandeep.kod...@gmail.com> wrote:
>>
>>> same here
>>> Cloned 100 files.
>>> Cloned 200 files.
>>> Cloned 300 files.
>>> Cloned 400 files.
>>> Cloned 500 files.
>>> Cloned 600 files.
>>> Cloning 414 application files.
>>> Rolling back the update.
>>> Error 500: --- begin server output ---
>>>
>>> 
>>> 
>>> 500 Server Error
>>> 
>>> 
>>> Error: Server Error
>>> The server encountered an error and could not complete your
>>> request.If th
>>> e problem persists, please http://code.google.com/appengine/community.h
>>> tml">report your problem and mention this error message and the
>>> query that c
>>> aused it.
>>> 
>>> 
>>>
>>> On Thu, Mar 15, 2012 at 3:38 PM, Nicanor Babula <
>>> nicanor.bab...@gmail.com> wrote:
>>>
 Hi,

 I tried 3 times in a row to deploy my application, but I keep getting
 the message below. I attached the specified log file too (it says pretty
 much the same thing).
 appid: domodentweb2
 datastore: HRD.

 What am I doing wrong?

 Thanks.

 error message:

 Cloning 2876 application files.
  on backend null.
 com.google.appengine.tools.admin.HttpIoException: Error posting to URL:
 https://appengine.google.com/api/appversion/clonefiles?app_id=s%7Edomodentweb2&version=7d&;
 500 Internal Server Error

 
 
 500 Server Error
 
 
 Error: Server Error
 The server encountered an error and could not complete your
 request.If the problem persists, please http://code.google.com/appengine/community.html";>report your
 problem and mention this error message and the query that caused it.
 
 

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

>>>
>>>
>>>
>>> --
>>> Regards
>>> Sandeep Koduri
>>> Phone: +91- 99 666 02 456
>>> Gtalk: sandeep.koduri | Skype: sandeep.koduri
>>> P Please consider the environment before printing this email
>>>
>>>  --
>>> 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.
>>>
>>
>>
>>
>> --
>> Nicanor Cristian Babula
>>
>>
>>  --
>> 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.
>



-- 
Nicanor Cristian Babula

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

Re: [google-appengine] Deploy fails

[Andrin von Rechenberg]

It's extremely slow for me too
appid: miumeet-hr

On Thu, Mar 15, 2012 at 11:11 AM, Nicanor Babula
wrote:

> I wouldn't want to be in the appengine team right now... ;) Hope they'll
> fix this soon.
>
>
> On Thu, Mar 15, 2012 at 11:09 AM, Sandeep Koduri  > wrote:
>
>> same here
>> Cloned 100 files.
>> Cloned 200 files.
>> Cloned 300 files.
>> Cloned 400 files.
>> Cloned 500 files.
>> Cloned 600 files.
>> Cloning 414 application files.
>> Rolling back the update.
>> Error 500: --- begin server output ---
>>
>> 
>> 
>> 500 Server Error
>> 
>> 
>> Error: Server Error
>> The server encountered an error and could not complete your
>> request.If th
>> e problem persists, please http://code.google.com/appengine/community.h
>> tml">report your problem and mention this error message and the query
>> that c
>> aused it.
>> 
>> 
>>
>> On Thu, Mar 15, 2012 at 3:38 PM, Nicanor Babula > > wrote:
>>
>>> Hi,
>>>
>>> I tried 3 times in a row to deploy my application, but I keep getting
>>> the message below. I attached the specified log file too (it says pretty
>>> much the same thing).
>>> appid: domodentweb2
>>> datastore: HRD.
>>>
>>> What am I doing wrong?
>>>
>>> Thanks.
>>>
>>> error message:
>>>
>>> Cloning 2876 application files.
>>>  on backend null.
>>> com.google.appengine.tools.admin.HttpIoException: Error posting to URL:
>>> https://appengine.google.com/api/appversion/clonefiles?app_id=s%7Edomodentweb2&version=7d&;
>>> 500 Internal Server Error
>>>
>>> 
>>> 
>>> 500 Server Error
>>> 
>>> 
>>> Error: Server Error
>>> The server encountered an error and could not complete your
>>> request.If the problem persists, please http://code.google.com/appengine/community.html";>report your
>>> problem and mention this error message and the query that caused it.
>>> 
>>> 
>>>
>>>  --
>>> 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/-/H3CTrmVDZTwJ.
>>> 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.
>>>
>>
>>
>>
>> --
>> Regards
>> Sandeep Koduri
>> Phone: +91- 99 666 02 456
>> Gtalk: sandeep.koduri | Skype: sandeep.koduri
>> P Please consider the environment before printing this email
>>
>>  --
>> 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.
>>
>
>
>
> --
> Nicanor Cristian Babula
>
>
>  --
> 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] local datastore corrupted

[hugues2]

Hi,

Just got the datastore on my local dev machine emptied after a out of 
memory error on GAE. Did it happen to anyone else ? If so, is there a 
reproductible case ?

Appengine sdk version is appengine-api-1.0-sdk-1.6.3.jar

Cheers,

Hugues

-- 
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/-/zKuCIO7odPsJ.
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] Storing from PDF to IMG

[Max]

Dear All,
I'm always storing the img I receive in the blobstore using this code:

class UploadHandler(blobstore_handlers.BlobstoreUploadHandler):
 def post(self):
 upload_files = self.get_uploads('File')
 blob_info = upload_files[0]
 fotos = FOTO()
 fotos.link = blob_info.key()
 fotos.Tlink = images.get_serving_url(fotos.link, 94)
 fotos.Glink = images.get_serving_url(fotos.link, 800)
 fotos.put()

Now I receive a PDF and I have to store an IMG.
And I'm thinking to use the conversions tool as per below.

from google.appengine.api import conversion

# Create a conversion request from HTML to PNG.
asset = conversion.Asset("text/html", "some data", "test.html")
conversion_obj = conversion.Conversion(asset, "image/png")

result = conversion.convert(conversion_obj)
if result.assets:
  # Note: in most cases, we will return data all in one asset.
  # Except that we return multiple assets for multiple pages image.
  for asset in result.assets:
doSomethingWithAsset(asset.data)
else:
  handleError(result.error_code, result.error_text)


My question is:
How can I store the asset? Could I still use the way I was?

Thanks

Max

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

Re: [google-appengine] Deploy fails

[Nicanor Babula]

I wouldn't want to be in the appengine team right now... ;) Hope they'll
fix this soon.

On Thu, Mar 15, 2012 at 11:09 AM, Sandeep Koduri
wrote:

> same here
> Cloned 100 files.
> Cloned 200 files.
> Cloned 300 files.
> Cloned 400 files.
> Cloned 500 files.
> Cloned 600 files.
> Cloning 414 application files.
> Rolling back the update.
> Error 500: --- begin server output ---
>
> 
> 
> 500 Server Error
> 
> 
> Error: Server Error
> The server encountered an error and could not complete your
> request.If th
> e problem persists, please http://code.google.com/appengine/community.h
> tml">report your problem and mention this error message and the query
> that c
> aused it.
> 
> 
>
> On Thu, Mar 15, 2012 at 3:38 PM, Nicanor Babula 
> wrote:
>
>> Hi,
>>
>> I tried 3 times in a row to deploy my application, but I keep getting the
>> message below. I attached the specified log file too (it says pretty much
>> the same thing).
>> appid: domodentweb2
>> datastore: HRD.
>>
>> What am I doing wrong?
>>
>> Thanks.
>>
>> error message:
>>
>> Cloning 2876 application files.
>>  on backend null.
>> com.google.appengine.tools.admin.HttpIoException: Error posting to URL:
>> https://appengine.google.com/api/appversion/clonefiles?app_id=s%7Edomodentweb2&version=7d&;
>> 500 Internal Server Error
>>
>> 
>> 
>> 500 Server Error
>> 
>> 
>> Error: Server Error
>> The server encountered an error and could not complete your
>> request.If the problem persists, please http://code.google.com/appengine/community.html";>report your problem
>> and mention this error message and the query that caused it.
>> 
>> 
>>
>>  --
>> 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/-/H3CTrmVDZTwJ.
>> 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.
>>
>
>
>
> --
> Regards
> Sandeep Koduri
> Phone: +91- 99 666 02 456
> Gtalk: sandeep.koduri | Skype: sandeep.koduri
> P Please consider the environment before printing this email
>
>  --
> 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.
>



-- 
Nicanor Cristian Babula

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

Re: [google-appengine] Deploy fails

[Sandeep Koduri]

same here
Cloned 100 files.
Cloned 200 files.
Cloned 300 files.
Cloned 400 files.
Cloned 500 files.
Cloned 600 files.
Cloning 414 application files.
Rolling back the update.
Error 500: --- begin server output ---



500 Server Error


Error: Server Error
The server encountered an error and could not complete your
request.If th
e problem persists, please http://code.google.com/appengine/community.h
tml">report your problem and mention this error message and the query
that c
aused it.



On Thu, Mar 15, 2012 at 3:38 PM, Nicanor Babula wrote:

> Hi,
>
> I tried 3 times in a row to deploy my application, but I keep getting the
> message below. I attached the specified log file too (it says pretty much
> the same thing).
> appid: domodentweb2
> datastore: HRD.
>
> What am I doing wrong?
>
> Thanks.
>
> error message:
>
> Cloning 2876 application files.
>  on backend null.
> com.google.appengine.tools.admin.HttpIoException: Error posting to URL:
> https://appengine.google.com/api/appversion/clonefiles?app_id=s%7Edomodentweb2&version=7d&;
> 500 Internal Server Error
>
> 
> 
> 500 Server Error
> 
> 
> Error: Server Error
> The server encountered an error and could not complete your
> request.If the problem persists, please http://code.google.com/appengine/community.html";>report your problem
> and mention this error message and the query that caused it.
> 
> 
>
>  --
> 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/-/H3CTrmVDZTwJ.
> 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.
>



-- 
Regards
Sandeep Koduri
Phone: +91- 99 666 02 456
Gtalk: sandeep.koduri | Skype: sandeep.koduri
P Please consider the environment before printing this email

-- 
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] Deploy fails

[Nicanor Babula]

Hi,

I tried 3 times in a row to deploy my application, but I keep getting the 
message below. I attached the specified log file too (it says pretty much 
the same thing). 
appid: domodentweb2
datastore: HRD.

What am I doing wrong?

Thanks.

error message:

Cloning 2876 application files.
 on backend null.
com.google.appengine.tools.admin.HttpIoException: Error posting to URL: 
https://appengine.google.com/api/appversion/clonefiles?app_id=s%7Edomodentweb2&version=7d&;
500 Internal Server Error



500 Server Error


Error: Server Error
The server encountered an error and could not complete your 
request.If the problem persists, please http://code.google.com/appengine/community.html";>report your 
problem and mention this error message and the query that caused it.



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



appengine-deploy4363645072756841701.log
Description: Binary data

[google-appengine] timed out on datastore operations!

[Sandeep Koduri]

Hi,

Any one facing same issues

http://code.google.com/status/appengine/detail/datastore/2012/03/15#ae-trust-detail-datastore-get-latency


Or any thing on my ID?[?][?][?]

-- 
Regards
Sandeep Koduri
Phone: +91- 99 666 02 456
Gtalk: sandeep.koduri | Skype: sandeep.koduri
P Please consider the environment before printing this email

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

<<364.gif>>

[google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Tapir]

On Mar 14, 11:00 pm, Jeff Schnitzer  wrote:
> On Wed, Mar 14, 2012 at 4:28 AM, Tapir  wrote:
>
> > On Mar 14, 1:17 pm, Gopal Patel  wrote:
> >> you mean, always have one instance more than required ? ( who is going to
> >> pay for that ? ) , and is not minimum idle instance same thing ?
>
> > It is different with the normal resident instance.
> > It is an instance to handle requests only at the time of the situation
> > "no available instances and need create a new instance",
> > so that many "Cold Starts" can be avoided.
>
> This is pretty much exactly what setting minimum idle instances does.
> Requests are preferentially routed to dynamic instances rather than
> resident instances.
>
> The problem is, something in the scheduler is broken.  Instead of
> routing requests to the idle instance, GAE prefers to route requests
> to a fresh instance, causing the user to wait while an instance warms
> up.  That setting is probably best described as "minimum useless
> instances".  Maybe somebody took the "minimum _idle_ instances" label
> too literally ;-)
>
> This is the behavior I observed a week or two ago.  Hopefully it will
> be fixed.  Doesn't sound like it has been so far.

Yes, here is usual case of the scheduler do it wrong:
- one resident instance and it is handling a request and the handling
is expected to be finished in 0.3 second.
- a new request comes, the scheduler prepares to create and initialize
a new instance, this need about 15 seconds to finish.
- ok, now the scheduler do a wrong job, it let the new request wait
for 15 seconds and be handled by the new instance.
  It is TOTALLY WRONG! The scheduler should let the resident instance
handle the new request, too!

So it seems the problem is the scheduler maintain a request queue for
every instance. It is not a good implementation.
The scheduler should maintain a request queue for every app!

>
> Jeff

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

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Mark Rathwell]

> The way it is supposed to work with min idle instances set is:
> - idle instance is warm and ready (let's call it I1)
> - request comes in
> - request goes to the idle instance at which point another instance is
> immediately spun up (let's call it I2)
> - you now have 1 idle instance (I2) as well as 1 instance serving traffic
> (I1)

My experiences have been similar to Tapir over the last month or so.
I have an app that I have been testing to try to duplicate the always
on behavior in the new setup.  This app has not been updated, etc., in
that time, billing is enabled, no datastore access, or any other
services, just dynamically generated html.

First, I tried the automatic setting for idle instances, and did not
keep track, but visiting the app about once a day I noticed that many
of those requests were loading requests, taking 20-35 seconds to load,
with subsequent requests performing fine.

Next, I tried setting idle instances to 1, and visiting about once a
day, 7 out of 10 initial requests to the app were loading requests,
with subsequent requests performing fine.

Finally, I tried setting idle instances to 2, and visiting about once
a day, only 3 out of 9 initial requests were loading requests.  So,
better with 2, but still not what I would consider acceptable.

If this is the expected behavior, I would suggest that it probably shouldn't be.

 - Mark

On Thu, Mar 15, 2012 at 3:54 AM, Gregory D'alesandre  wrote:
> Hey Jeff,
>
> The way it is supposed to work with min idle instances set is:
> - idle instance is warm and ready (let's call it I1)
> - request comes in
> - request goes to the idle instance at which point another instance is
> immediately spun up (let's call it I2)
> - you now have 1 idle instance (I2) as well as 1 instance serving traffic
> (I1)
>
> I know it might seem like we are taking the label too literally but we are
> trying to maintain idle capacity for you.  The tricky part is since we
> always spin up a new idle instance when an existing one begins to serve
> traffic it looks like they are sitting around unused when they are in fact
> being used often just others immediately take their place.  Are you sure
> this is not the behavior your are observing?
>
> Thanks,
>
> Greg
>
> On Wed, Mar 14, 2012 at 8:00 AM, Jeff Schnitzer  wrote:
>>
>> On Wed, Mar 14, 2012 at 4:28 AM, Tapir  wrote:
>> >
>> > On Mar 14, 1:17 pm, Gopal Patel  wrote:
>> >> you mean, always have one instance more than required ? ( who is going
>> >> to
>> >> pay for that ? ) , and is not minimum idle instance same thing ?
>> >
>> > It is different with the normal resident instance.
>> > It is an instance to handle requests only at the time of the situation
>> > "no available instances and need create a new instance",
>> > so that many "Cold Starts" can be avoided.
>>
>> This is pretty much exactly what setting minimum idle instances does.
>> Requests are preferentially routed to dynamic instances rather than
>> resident instances.
>>
>> The problem is, something in the scheduler is broken.  Instead of
>> routing requests to the idle instance, GAE prefers to route requests
>> to a fresh instance, causing the user to wait while an instance warms
>> up.  That setting is probably best described as "minimum useless
>> instances".  Maybe somebody took the "minimum _idle_ instances" label
>> too literally ;-)
>>
>> This is the behavior I observed a week or two ago.  Hopefully it will
>> be fixed.  Doesn't sound like it has been so far.
>>
>> Jeff
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

-- 
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: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Tapir]

On Mar 15, 3:54 pm, "Gregory D'alesandre"  wrote:
> Hey Jeff,
>
> The way it is supposed to work with min idle instances set is:
> - idle instance is warm and ready (let's call it I1)
> - request comes in
> - request goes to the idle instance at which point another instance is
> immediately spun up (let's call it I2)
> - you now have 1 idle instance (I2) as well as 1 instance serving traffic
> (I1)

Do you mean this is how the current GAE instance scheduler is
implemented?
>From my observations, sometimes the request will not go to the idle
instance but wait many seconds to go the new created instance.
I can confirm the idle instance is really idle, for in the observation
period, it didn't handle any new requests.
It is a bug? Or the machine the idle resident instance hosted on has
no free CPU?
I means "many apps are hosted the same machine, the resident instances
or the part of CPU we bought are not always available to us"?

>
> I know it might seem like we are taking the label too literally but we are
> trying to maintain idle capacity for you.  The tricky part is since we
> always spin up a new idle instance when an existing one begins to serve
> traffic it looks like they are sitting around unused when they are in fact
> being used often just others immediately take their place.  Are you sure
> this is not the behavior your are observing?
>
> Thanks,
>
> Greg
>
>
>
>
>
>
>
> On Wed, Mar 14, 2012 at 8:00 AM, Jeff Schnitzer  wrote:
> > On Wed, Mar 14, 2012 at 4:28 AM, Tapir  wrote:
>
> > > On Mar 14, 1:17 pm, Gopal Patel  wrote:
> > >> you mean, always have one instance more than required ? ( who is going
> > to
> > >> pay for that ? ) , and is not minimum idle instance same thing ?
>
> > > It is different with the normal resident instance.
> > > It is an instance to handle requests only at the time of the situation
> > > "no available instances and need create a new instance",
> > > so that many "Cold Starts" can be avoided.
>
> > This is pretty much exactly what setting minimum idle instances does.
> > Requests are preferentially routed to dynamic instances rather than
> > resident instances.
>
> > The problem is, something in the scheduler is broken.  Instead of
> > routing requests to the idle instance, GAE prefers to route requests
> > to a fresh instance, causing the user to wait while an instance warms
> > up.  That setting is probably best described as "minimum useless
> > instances".  Maybe somebody took the "minimum _idle_ instances" label
> > too literally ;-)
>
> > This is the behavior I observed a week or two ago.  Hopefully it will
> > be fixed.  Doesn't sound like it has been so far.
>
> > Jeff
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google App Engine" group.
> > To post to this group, send email to google-appengine@googlegroups.com.
> > To unsubscribe from this group, send email to
> > google-appengine+unsubscr...@googlegroups.com.
> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.

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

Re: [google-appengine] Very high latency since March 13th

[andidol]

I'm doing a Model.get_by_key_name().. on a model with ~50 million entries 
(I know this should not effect the query-time). The Model.get_by_key_name() 
method often takes more than 200ms for finding an entry, not every time but 
often. Not finding a key fails much faster, IMO this is ok. I think this is 
not normal, do you have any suggestions?

On Wednesday, March 14, 2012 8:01:26 PM UTC+1, Ikai Lan wrote:
>
> We're addressing issues with high replication datastore applications. 
>
> In the future, however, this information is typically not enough. What are 
> you doing? Are you making datastore calls? Are you doing URLFetch? Are you 
> making XMPP or email API calls? Are CPU intensive tasks slower? This is 
> important because there are a lot of operations for which 200ms would seem 
> low latency. If you're trying to brute force SHA1 hashes and it's taking 
> 500ms on average, you're doing okay.
>
> One of the fortunate things about working with software developers instead 
> of normal internet consumers is that I can usually just give the guidance, 
> "report issues that way you want your users to report issues or bugs", and 
> it gets the message across =).
>
> --
> Ikai Lan 
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
>
>
> On Wed, Mar 14, 2012 at 5:48 AM, andidol wrote:
>
>> Hi,
>>
>> I have very high latency on my AppEngine since yesterday. It was really 
>> fast before < 100ms. Now there are a lot of requests performing with > 
>> 200ms without any reason. I did not update or did anything.
>> I'm using High Replication Datastore.
>>
>> 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/-/UKDaOm5bNJsJ.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>
>

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

Re: [google-appengine] Re: It seems "Cold Starts" is an unavoidable problem for GAE. So why not to conquer it?

[Gregory D'alesandre]

Hey Jeff,

The way it is supposed to work with min idle instances set is:
- idle instance is warm and ready (let's call it I1)
- request comes in
- request goes to the idle instance at which point another instance is
immediately spun up (let's call it I2)
- you now have 1 idle instance (I2) as well as 1 instance serving traffic
(I1)

I know it might seem like we are taking the label too literally but we are
trying to maintain idle capacity for you.  The tricky part is since we
always spin up a new idle instance when an existing one begins to serve
traffic it looks like they are sitting around unused when they are in fact
being used often just others immediately take their place.  Are you sure
this is not the behavior your are observing?

Thanks,

Greg

On Wed, Mar 14, 2012 at 8:00 AM, Jeff Schnitzer  wrote:

> On Wed, Mar 14, 2012 at 4:28 AM, Tapir  wrote:
> >
> > On Mar 14, 1:17 pm, Gopal Patel  wrote:
> >> you mean, always have one instance more than required ? ( who is going
> to
> >> pay for that ? ) , and is not minimum idle instance same thing ?
> >
> > It is different with the normal resident instance.
> > It is an instance to handle requests only at the time of the situation
> > "no available instances and need create a new instance",
> > so that many "Cold Starts" can be avoided.
>
> This is pretty much exactly what setting minimum idle instances does.
> Requests are preferentially routed to dynamic instances rather than
> resident instances.
>
> The problem is, something in the scheduler is broken.  Instead of
> routing requests to the idle instance, GAE prefers to route requests
> to a fresh instance, causing the user to wait while an instance warms
> up.  That setting is probably best described as "minimum useless
> instances".  Maybe somebody took the "minimum _idle_ instances" label
> too literally ;-)
>
> This is the behavior I observed a week or two ago.  Hopefully it will
> be fixed.  Doesn't sound like it has been so far.
>
> Jeff
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to google-appengine@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

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

[google-appengine] Re: Javaland scheduler behavior

[Mauricio Aristizabal]

Jason, how do you know you must have a resident instance to get warmup 
requests to work?  I don't see this anywhere in the docs. And to enable one 
do I just define a backend in backends.xml?

I'm pretty sure warmups were working for me before but haven't seen them 
happening in the logs for a while now. I don't know if I did anything on my 
end but I've been trying to turn them on and nothing I do works.

thanks


On Thursday, March 8, 2012 7:53:32 PM UTC-8, Jason Collins wrote:
>
> Jeff, I see very similar behaviour in pythonland - i.e., the resident 
> instance gets almost no traffic. I opened an Enterprise support ticket 
> on the topic, and I got the following response: 
>
> "the Resident instances are kept alive by the GAE scheduler for long 
> periods in order to attend to new requests whenever there are no 
> Dynamic instances to serve them. In this way, the request does not 
> have to wait for the instance creation, thus, the latency of creating 
> the instance is avoided. 
> However, as soon as the new Dynamic instance is up and running, it 
> starts getting requests and the Resident instance turns idle again, 
> until the app sees more traffic than its available Dynamic instances 
> are able to serve." 
>
> Frankly, I'm not totally sure when the resident instances actually get 
> traffic. I flipped on a resident instance just so that I could get 
> warmup requests back (they are only issued if you have resident 
> instances now), but now I have an instance floating around doing very, 
> very little work. 
>
> It just seems wrong to me. 
> j 
>
>
>

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