Hello Richard, I'm glad to hear you were able to resolve your issue. There
is no explicitly documented relation between the latency and the size of
the result set, other than to say the former is dependent on the latter.
This should effectively be a linear relationship.
On Sunday, September 3,
I couldn't use a projection query on the PickleProperty I wanted it was too
large to index
On Saturday, September 2, 2017 at 9:10:15 PM UTC+3, Alex Martelli wrote:
>
> To fetch only some of an entity's properties, consider a projection query,
> e.g
> https://cloud.google.com/appengine/docs/sta
To fetch only some of an entity's properties, consider a projection query,
e.g
https://cloud.google.com/appengine/docs/standard/python/datastore/projectionqueries
Alex
On Sat, Sep 2, 2017 at 6:41 PM, Richard Cheesmar
wrote:
> Hi, Yannick,
>
> I have solved the issue :).
>
> What I had to do wa
Hi, Yannick,
I have solved the issue :).
What I had to do was take the main property of the model entities that I
need to send to the client and and save them to another new model.
The subsequent query does not require any equality tests on properties just
a straight fetch_page and returns th
Hello Richard,
I referred you to the best practices because depending on your use case any
one of them might be the key to your performance issues. In Cloud Datastore
there are only 2 factors that determine the speed of your query.
The first of those is indexing, keeping in mind that you cannot
Interestingly, I have another query which is identical except for one more
entity comparison
result, next_cursor, more = MyModel.query(MyModel.active == True,
MyModel.offline == False,
MyModel.location.alpha2 == alpha2).fetch_page(pagination, start_cursor=cursor)
This query is infinitely faste
Yannick,
Could you please point out why the reference to query best practices when
the query is clearly defined above. It's a simple page fetch with two
conditions, and as described is taking 2 seconds on average to fetch 250
results and 4 seconds for 550 results on the live version...
At the
Hi, Yannick,
Yes they are fairly large and have several pickleProperties with lists of
properties and some json elements. Yes an Indexes are there for the two
query params active and offline in that model
--
You received this message because you are subscribed to the Google Groups
"Google Ap
Hello Richard, since you're not mentioning it could you tell us whether or
not you've defined indexes for this specific query? There's also no
indication of how large these entities are. Do you get the same issues for
other kind of entities?
You should read through the queries best practices
