5 put() RPCs plus one more for the commit, although you could use a batch
put to turn this into 1 put() RPC plus one more for the commit. These are
implementation details though. We may at some point just hold on to the
entire mutation until commit time (easy if you're not asking us to generate
It is pseudo code. To be detailed, you have to store it as byte array
inside a Blob.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this discussion on the web visit
Thank you, Ikai. Your comments were useful. I was fixated on one
object one entity. Following your advice, I collapsed the entities.
Now, they are only handful.
One last doubt - how does writing to the disk work in the following
scenario ?
// transaction 1
// set two objects as properties
// no
Thanks, Jeff. I understand that an entity is a blob from serialization
point of view. I thought that there is a notion of sub-blob
corresponding to each property and that when a property is updated,
only a sub-blob is written out to disk. You clarified that this is not
the case. Thanks.
But,
If there is no need to reference the objects from outside the group, you
would probably find it a lot more efficient to store the while array
serialized as a byte array.
--
You received this message because you are subscribed to the Google Groups
Google App Engine for Java group.
To view this
Thank you, Gerald. I will look for alternative implementations if I
can not call put() many times within a transaction. I am waiting for
Ikai's comments.
J.Ganesan
On Nov 4, 11:02 am, Gerald Tan woefulwab...@gmail.com wrote:
If there is no need to reference the objects from outside the group,
If all 4000 entites are in a single entity group, in theory you can do this
because it counts as a single transactional write. There's a maximum RPC
size of 11mb (implementation detail) so if you trip this, you're in some
trouble - the RPC size include not only the size of the entity but also the
On Fri, Nov 4, 2011 at 3:56 PM, Ikai Lan (Google) ika...@google.com wrote:
If all 4000 entites are in a single entity group, in theory you can do this
because it counts as a single transactional write. There's a maximum RPC
size of 11mb (implementation detail) so if you trip this, you're in
On Nov 4, 6:00 am, Ikai Lan (Google) ika...@google.com wrote:
I'm confused ... an Object[] array? This is bad for a ton of reasons.
Calling put() 4000 times in a single request is just bad for a lot of
reasons.
I'm not sure I understand what problem you are trying to solve. Can you
explain
