[google-appengine] Re: Performance of new gcloud-java API

Hi, Nick: Sorry, I don't know the appId and only have project Id. But I found the first time insertion spent over 2 secs and the second time (or later) insertion spent about 500 ms. It seems the first time insertion will do some preparations or initial actions. I am wondering if there is any po

[google-appengine] Re: Performance of new gcloud-java API

Thanks for the quick response! Could you let us know the app ID so we could take a look at the Datastore statistics? This does indeed seem unexpected. You may wish to use mtr to test the IP route latency between your instance and our servers. You ca

[google-appengine] Re: Performance of new gcloud-java API

Hi, Nick: We build up a server on AWS and try to insert/query datastore data. The entity is not large and only insert/query one entity. Please help to check the following entity (I used these data to test performance). Thank you for your prompt reply. *Name/ID* (String) name=9c3248df-4e02-447a-8b

[google-appengine] Re: Performance of new gcloud-java API

Hey Ifen, 2 to 2.8 seconds for a single entity put sounds like a serious outlier. Are you seeing that kind of timing for each put? Where is your code running - on your own computer, a Compute Engine instance, inside App Engine, a custom runtime in the Fl

[google-appengine] Re: Performance of new gcloud-java API

Hi, I'm also a Java developer and in Linux platform. I am using the gcloud-java for operating datastore and that is a really good library. However, the query/insert performance is not good even I don't count the connection time. >From my testing experience, the average time of inserting and quer

[google-appengine] Re: Performance of new gcloud-java API

It's an interesting question. Obviously empirical testing is best, but one could investigate the source code to make an informed guess as to the efficiency. Really the native App Engine runtime API's benefit from using gRPC , rather than JSON, but I feel that the gclou