Skip to content

Google cloud datastore slow. >1 sec / query #190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nojvek opened this issue Dec 8, 2017 · 3 comments
Closed

Google cloud datastore slow. >1 sec / query #190

nojvek opened this issue Dec 8, 2017 · 3 comments

Comments

@nojvek
Copy link

nojvek commented Dec 8, 2017

We've been getting consistent greater than 1 second on average calls from gcds. Not sure why its ridiculously slow.

We are using it from python.

from google.cloud import datastore

client = datastore.Client('foo', 'bar')
client.query(
  kind='Blah',
  filters=(
      ('name', '=', 'yolo'),
  ),
  order=('timestamp',)
)

print(list(query.fetch()))

Very simple call but consistently very slow.

Related to #154, but I see that is already closed.

@nojvek nojvek changed the title Google cloud datastore slow. > 1 sec / query Google cloud datastore slow. >1 sec / query Dec 8, 2017
@wsh
Copy link
Contributor

wsh commented Dec 8, 2017

Hey there--this repo is for the low-level google-cloud-datastore client (which has package google.datastore). You're using google-cloud-python, which is great (!), but a separate repo. Please file an issue there and we can look into this.

@wsh wsh closed this as completed Dec 8, 2017
@zappan
Copy link

zappan commented Jan 2, 2018

@wsh I'm having the same issue of DB insert being slow, ran once in 10 minutes (data arriving from some IoT device) - using Node, not Python, and there is the similar topic #154 where you also redirect people to the higher level datastore client, while it's obvious that the issue is present across client libs.

Also, your project structure is something known to you internally, for us outside users, it's not that well known, and as I see no cross-links, look like people fell out of your funnel in reporting these issues in those places. I hope you understand that different points of view are heavily different here, yours from the inside, and ours from the outside.

It would be highly appreciated if you could actually do that extra step for your users, and open the issues in the places where you find it necessary to be opened, and link this and the above-mentioned issues from those, and cross-link to them here for tracking, if you still think they belong in client libs (although it seems the issue is somewhere else, like people already mentioned, it's happening in different environments).

Thanks for understanding, and I hope you'll do some steps in the right direction with this. Cheers

---- UPDATE ----
Okay, found one report in the higher level lib, linking it here for a reference: googleapis/nodejs-datastore#9

@wsh
Copy link
Contributor

wsh commented Apr 8, 2018

@zappan: completely agreed that our repo structure here is confusing. The reason I've avoided copying issues myself is that I didn't want to screw up the metadata. Turns out we have a tool (google/github-issue-mover) for doing that, which makes it way easier to preserve that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants