I’m working with Google now on this, providing monitoring, trace, other 
metrics. I don’t think it’s working as documented. Closing this thread.

 

From: Bret Lowery <[email protected]>
Date: Tuesday, May 24, 2016 at 7:29 PM
To: <[email protected]>
Subject: Re: [google-appengine] Re: GAE memory quotas should be per version per 
instance, not just per instance

 

Yes. I can load my new version fine and it runs fine alone, but I want to be 
able to test the new version on the prod instance before I swap traffic over to 
the new version. Otherwise I have to shut down the old version, shutting off 
live traffic when I switch while I test my new version before I officially send 
traffic to it. The great thing about versions to me is that I can run them 
simultaneously so I keep traffic up on prod and I test my prod environ on the 
new version at the same time.

 

For those who aren’t aware, you can run (or more!) two versions simultaneously 
on one instance. Example:

 

Say app.yaml version is set to “1”.

 

Version 1 (“default”) when deployed will run at 
http://yourprojectname.appspot.com

 

Change app.yaml version to “2” and upload.

 

Version 2 will upload to http://2.yourprojectname.appspot.com. It won’t become 
the default version at http://yourprojectname.appspot.com until you swap your 
live traffic over to it 100% (a feature available from the dashboard). Then, it 
automagically becomes http://yourprojectname.appspot.com.

 

But, in between, you can run side by side, and send GETs/POSTs directly to 
http://2.yourprojectname.appspot.com to unit test the new version while the 
previous version is still live as the default version on the default URL. 
That’s what I’m trying to do, and that as I understood it is why Google allows 
you to do it this way.

 

From: 'Josh Moore' via Google App Engine <[email protected]>
Reply-To: <[email protected]>
Date: Tuesday, May 24, 2016 at 7:01 PM
To: <[email protected]>
Subject: Re: [google-appengine] Re: GAE memory quotas should be per version per 
instance, not just per instance

 

For clarification, are you saying that if you only have one version available 
at a time, you can load the alternate version successfully?  

 

On Tue, May 24, 2016 at 3:35 PM, Bret Lowery <[email protected]> wrote:

FYI here is the error you get in the GAE log:

"<timestamp> Exceeded soft private memory limit of 128 MB with xxx MB after 
servicing yyy requests total" (xxx,yyy = some numbers)

On Tuesday, May 24, 2016 at 6:03:16 PM UTC-4, Bret Lowery wrote:

Suppose GAE only supported a maximum of two versions per instance at 128MB max 
memory per instance on the default F1 config. Suppose Version 1 of your app 
uses exactly 64MB memory at startup. In that case, you can't start Version 2 of 
you app if it uses so much as one byte more memory than version 1, since 64MB + 
64MB + 1 byte > 128MB. (Yes, it's a soft limit, but here's my point-->). What's 
the purpose of versions then? It isn't testing two versions side by side on the 
same instance in this case because one can't. 

 

I actually have this problem now. I have an app that starts up at 50MB and have 
added a feature that increases it to 100MB (some large in-memory hash lookups 
were added). However, I can't run them side by side on one F1 instance as I 
exceed my 128MB capacity, when *both individually* are under 128MB. 

 

I should be able to do this. What exactly is the point of GAE versions 
otherwise? I should be able to stand up both and route traffic to both via the 
provided features to do so without production failing due to this problem.

 

Also posted to Stackoverflow:

http://stackoverflow.com/questions/37402912/google-app-engine-memory-quotas-should-be-per-version-per-instance-not-just-per

 

 

 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/80a91ad7-1d02-4f7a-876b-194f43f4a6bc%40googlegroups.com.


For more options, visit https://groups.google.com/d/optout.



 

-- 

 

Josh Moore | Cloud Solutions Engineer | [email protected] | 

 

-- 
You received this message because you are subscribed to a topic in the Google 
Groups "Google App Engine" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/google-appengine/SpHldXOfJl0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
[email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAOvpJmWAX1R7ciX8Uy7yK%3DRQbZGbBUZCecc7u%3DWNuUaEDavSNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.



-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/A0EEE77A-4CA0-4385-81A2-C27FE59CE10E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to