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 query one
entity (4 properties) is about 2000~2800ms/200~600ms.
Could you please let me know that is it possible to improve the performance?
or does your team have plan to improve the performance?? Thanks.
*Version: 0.2.1*
// Initialize
DatastoreOptions options = DatastoreOptions.builder()
.authCredentials(AuthCredentials.createForJson(new
FileInputStream(mCertJsonFile)))
.projectId(mProjectId).namespace(mNamespace).build();
mDatastore = options.service();
// [query] start to log time
mDatastore.run(Query.entityQueryBuilder().kind(KIND_NAME).build())
// [query] end to log time *=> average: 200~600ms*
// [insert] start to log time
mDatastore.put(entity)
// [insert] end to log time *=> average: 2000~2800ms*
On Thursday, 18 February 2016 08:59:19 UTC+8, Nick (Cloud Platform Support)
wrote:
>
> 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 <http://www.grpc.io/docs/>, rather than JSON, but I feel that the
> gcloud-java library will likely also be able to make use of the more
> efficient gRPC when in a suitable environment, falling back to HTTP JSON
> REST when necessary. I'll try to update this thread tomorrow with any of my
> findings from investigating the source of gcloud-java
> <https://github.com/GoogleCloudPlatform/gcloud-java>.
>
>
> On Wednesday, February 17, 2016 at 4:19:33 PM UTC-5, Robert Fox wrote:
>>
>> I'm a Java developer on Googles App Engine platform. Lately I've been
>> using Managed VMs. According to new-ish documentation on Google's site [1
>> <https://cloud.google.com/appengine/docs/managed-vms/java/migrating-an-existing-app>
>> ]:
>>
>> As you become more familiar with the Managed VM environment you should
>>> use the native features of the Java runtime and the Google Cloud client
>>> libraries for Java rather than App Engine SDKs.
>>> I love that the new gcloud-java seems to be a unified API for
>>> local/remote usage. But I do have one concern... and that is my question:
>>> How does performance compare to the standard App Engine APIs? I get worried
>>> with the new REST APIs with their JSON text processing / parsing... I will
>>> build a test suite if I have to but I was hoping someone might already know.
>>
>>
>> These new developments would seem to be a huge win for Compute Engine if
>> the new gcloud-java is performant and can run fully authenticated.
>>
>> Out of the following services I'm a heavy user of the four in bold.
>>
>> *Datastore*
>> Logging
>> *Memcache*
>> Search
>> *Task Queue*
>> *URL Fetch*
>> Users
>>
>>
--
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/1a3954fa-87ca-4522-91d8-a15d39e8b605%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
