One caveat: if you stuff too many entities (that are in a single entity
group) into a write, you'll hit an RPC limit exception. It's pretty hard to
trigger this, though. You'll need to be writing ~10mb+ worth of data in a
single write to trigger it.
--
Ikai Lan
Developer Programs Engineer, Google
I'm sure this is a FAQ but I haven't been able to find the answer so far.
I have read there's a limit of 2-3 writes per second per entry group. If you
batch out multiple entities that all have the same parent is this ok? Or does
it count as multiple writes? I understand it is multiple
From my experiments, writing large #s of entities to a single EG in a
batch put is quite fast and does not cause the throughput problem.
Jeff
On Tue, Feb 7, 2012 at 4:43 PM, Andrew Myers am2...@gmail.com wrote:
I'm sure this is a FAQ but I haven't been able to find the answer so far.
I have
Thanks Jeff. Much appreciated. I'm using Objectify too ;-)
On 8 February 2012 09:28, Jeff Schnitzer j...@infohazard.org wrote:
From my experiments, writing large #s of entities to a single EG in a
batch put is quite fast and does not cause the throughput problem.
Jeff
On Tue, Feb 7, 2012
Andrew, multiple writes of entities in a single batch put to the same
entity group count as 1 entity group write (but many more datastore write
ops - this might be confusing), so you won't run into contention issues.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com
Thanks Ikai. Appreciate the clarification!
All the best,
Andrew.
On 8 February 2012 11:42, Ikai Lan (Google) ika...@google.com wrote:
Andrew, multiple writes of entities in a single batch put to the same entity
group count as 1 entity group write (but many more datastore write ops -
this
