Thanks for clearing that up Ikai. I had designed my entities to have a
parent and many children using a List property on the parent.
I'll now change this to have an unowned relationship and use List
so that child entites are in their own entity group. This should solve
the contention issue.
On Jun
In general, a rule of thumb is to engineer your application for 1 write a
second to an entity group. If you are doing 2-5 writes a second to a single
entity, you *should* be okay, however, I would just as easily understand if
you are not. If you need to do "counters", the sharded counter pattern
sh
Yes each time a user makes a request to the app, their user entity is
loaded and their request count incremented, so the "User" entity is
fetched, updated and "put" very frequently.
Surely though the datastore should be able to handle this, it's not
like I'm making thousand of requests per second,
Hi,
Don't you have some datastore entities that are used in every request
or so? Let's say a global counter of requests or sthg equivalent.
That entity would be updated in every request, hence the contentions
as you trafic raises.
regards
ddoer
On Jun 22, 11:59 pm, mscwd01 wrote:
> Okay I jus
Okay I just got a single log entry pop up that may offer some insight
to the problem. It reads:
Too much contention on these datastore entities. please try again.
I have noticed a slight increase to the number of requests received
today (so far 40k), could it be some unforeseen issue that occurs
