[google-appengine] Re: Migrating to Compute Engine

Hello Thomas, By contrast to the standard environment, the Compute Engine environment would compare with a server you might simply run at home, in which case you have to provide what is automatically offered in the app engine standard environment. There is no scalability, so using one instan

[google-appengine] Re: Migrating to Compute Engine

Thanks for the answers! I already migrated my app to Flex Env using the compat runtime and noticed a great performance gain with only 1 permanent instance in comparison to automatic scaling in Standard Edition (10x more throughput showed by jmeter). Now that the compat runtime is deprecated I'll

[google-appengine] Re: Migrating to Compute Engine

Grüß Gott, Good news: you are perfectly right, it is still possible to access the Datastore of the legacy project when using the Cloud Client libraries, if you identify it with the same project ID. In fact, there is no need to launch a new project with a new ID just for your flex migration; yo

[google-appengine] Re: Migrating to Compute Engine

Very interesting, I'll try that as soon as possible! Dankeschön :) -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegrou

[google-appengine] Re: Migrating to Compute Engine

One more question before I do a test with the still available compat runtime on Flex Env: is it possible to have the legacy app running in the same project as the freshly ported Flex app just by using a different version name? Will it just add a GCE VM for that versioned instance and let the leg

[google-appengine] Re: Migrating to Compute Engine

If you don’t absolutely need the same app name with a different version to run in the new environment, there is the option to rename your new app and dedicate a new service to it, for the new environment, all under the same project. As a result, your old app would continue running in the standar

[google-appengine] Re: Migrating to Compute Engine

Thank you, but I'm not sure how to achieve this. I selected the project with my standard environment app in gcloud init and tried to deploy the flex version using appengine:deploy and the appengine-maven-plugin. This worked a few weeks ago with a new project, although it took about 15mins. This

[google-appengine] Re: Migrating to Compute Engine

Hello Thomas, Exactly as you supposed: the true entry now needs to read flex in your appengine-web.xml, or env: flex in the app.yaml file. You can see your logs in detail at /var/log/app_engine/custom_logs, as described in the “Using Cloud logging in App Engine apps” document

[google-appengine] Re: Migrating to Compute Engine

Thank you, unfortunately it's still not working. Now I found the logs of GCLOUD command and it says: 2016-11-30 07:07:41,608 DEBUGrootRetrying request to url https://www.googleapis.com/resumable/upload/storage/v1/b/staging.typingscout-test3.appspot.com/o?uploadType=resumable&alt=

[google-appengine] Re: Migrating to Compute Engine

In the log I could also see that src.tgz (146MB) is being uploaded for 6 minutes and then the host computer shuts down the connection because of a read timeout. What can I do about it? Am Mittwoch, 30. November 2016 07:16:20 UTC+1 schrieb Thomas Baldauf: > > Thank you, unfortunately it's still n

[google-appengine] Re: Migrating to Compute Engine

Hallo Thomas, What were you attempting to do exactly, when these logs got recorded? What was the exact command for deployment? If you tried to deploy to the flexible environment, was the standard environment app modified appropriately prior to the deployment attempt? You need to adapt

[google-appengine] Re: Migrating to Compute Engine

I just used the appengine-maven-plugin, which apparently is invoking gcloud under the hood. I was able to deploy the simple hello world example (https://github.com/GoogleCloudPlatform/getting-started-java/tree/master/helloworld-jsp) and modified it to access the datastore with the Google Cloud

[google-appengine] Re: Migrating to Compute Engine

Hello Thomas, Reproducing your code with Datastore access, I can see access times in the order of 200 to 300 ms, but for only one write and one final read. By contrast, your code accesses the Datastore for 28 times at each request, and it is there that the difference in timing is generated.

[google-appengine] Re: Migrating to Compute Engine

Thank you for investigating my issues. I'll try to follow your recommendations. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr..