Hey,
I've recently deployed a node.js application to a flex environment and I am
seeing some strange latency spikes of over 30 minutes. See below:
[image: Screenshot 2021-03-09 at 11.31.02.png]
CPU and memory usage are very low and I have checked the logs for any super
long requests.
Is there
I have an application running on standard env but I now need websocket
functionality. Is this likely to come to the standard env soon or should I
switch to flex?
Thanks!
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from
I heard that websockets for standard env is in the works, do we have an
estimated launch date or is it just a rumour?
On Friday, November 20, 2020 at 3:18:08 AM UTC sujeshth...@gmail.com wrote:
> Standard environment does not support we sockets yet.
> https://cloud.google.com/appengine/docs/the
Hey Alexander,
This sounds like the functionality I want. Perhaps I need to experiment
with a wild card certificate and avoid using the sub domains.
Thanks,
Alex
On Tuesday, July 14, 2020 at 4:04:38 PM UTC+1 a.not...@gmail.com wrote:
> Alex,
>
> We are doing just what you describe, although w
I'm trying to setup GAE with a custom sub domain and a specific version url.
For example I have an app running with the following setup
*VERSION_ID: 1234*
*SERVICE_ID: my-app*
*PROJECT_ID: my-project*
The provided url *https://1234-dot-my-app-dot-my-project.ew.r.appspot.com*
works
fine. But I c
But what if the build file is within a sub directory, how can you set the
dir to be its parent?
On Monday, June 1, 2020 at 8:44:27 PM UTC+1, David (Cloud Platform Support)
wrote:
>
> When you use the dir field in a build step, you are setting the working
> directory to its value and in this cas
Yes, I saw that SO issue but I couldn't work out what the correct dir:
value should be.
In both cases the app deploy successfully but in the second case when
accessing the url I receive a 500 error and the deployed code is only ~600
bytes which suggests to me it's deployed an empty folder or so
Hey,
I'm having trouble setting up my yaml files for google app engine. The
configuration works correctly when my app.yaml file is in the root of the
project but if it is within a subdirectory it does not build the correct
source. I suspect I need to set the `dir:` option in the build config, b
Yes.
I have implemented the warm up requests which has improved the performance
greatly.
So I understand, when a new instance is created what commands are run? Does
it have to do a npm install and copy over resources, or is there more?
Thanks!
On Tuesday, April 21, 2020 at 7:12:24 PM UTC+1,
So I managed to improved the load times by enabling "serverless" in the
next.js settings. This is enabled by default when deploying to ziet. I also
added the /_ah/start warmup which essentially just keeps the instance alive.
All getInitialProps are just returning some basic context and I'm using
I am deploying a next.js app to a Google App Engine (standard) but I am
having trouble with cold start times.
I am building locally then deploying the .next folder to GAE. On the first
boot it takes 15-25 seconds to boot up. Looking at the logs I can see a log
for a very long GET 200 request
11 matches
Mail list logo
