Let me also add that if what you’re observing regarding the F1 instance
memory allocation doesn't correspond to the official documentation provided
above, this is usually a sign of a public issue and should be further
investigated accordingly. You can open a new issue in the issue tracker
Thanks for the clarification as well, Jeff.
The information I provided above only applies to apps deployed using the
Java 8 runtime on GAE Standard, though. I’m currently not aware of
circumstances when a F1 instance would allocate 256 MB when in use with
Python 2.7 on GAE Standard.
In any
Thanks for the explanation. I'm using Python 2.7 on GAE standard so the
same issue must apply there as well.
On Fri, Jan 4, 2019 at 6:45 PM 'Tiago (Google Cloud Platform Support)' via
Google App Engine wrote:
> Hi,
>
> If you’re using the Java runtime on GAE Standard, since its updated from
>
Hi,
If you’re using the Java runtime on GAE Standard, since its updated from 32
to 64-bit in the Version 1.9.40, the Developer Console indeed reports a
higher memory [1] usage for all associated instances. Specifically, small
instances show double their sizes (in line with Jeff’s observation
128M is not enough to run a simple Java web app.
On Monday, December 31, 2018 at 5:25:26 PM UTC-4, Jeff O'Neill wrote:
>
> Hi George,
>
> My interest in upgrading is faster processors. I have some fairly
> computational tasks that I would like to get done more quickly.
>
> My F1 instances have
Hi George,
My interest in upgrading is faster processors. I have some fairly
computational tasks that I would like to get done more quickly.
My F1 instances have 256MB. They regularly go above 128MB and when they
exceed 256MB, I get this message in my logs:
Exceeded soft memory limit of 256
Hello Jeff,
You might have discovered a discrepancy in different documentation pages.
Where did you see 256MB value being indicated? Not aware of any similar
changes in F1 values right now.
What would you like to upgrade to? What specific advantages are you looking
for, with this
