The datastore will only update indexes that changed, so if s didn't change
you would only be charged 1 write op for the entity write (vs 0 write ops
if you didn't call put at all). I believe the dev_appserver only shows the
cost for inserting a new entity (which is substantially different from the
Hi Alfred,
Sorry for bringing this old topic back, I am also confused by the number
showed in the dev_appserver.
I think you meant
1 op for the entity
2x2 = 4 ops for each changed index value (1 remove, 1 add and two
directions)
My question is, do we need to do checks before calling put() to m
Thanks for the definitive clarification, Alfred.
It would be awesome if you guys could show the actual Read/Write Ops
incurred by each URI under the Current Load section of the live
dashboard.
On Sat, Sep 24, 2011 at 4:00 PM, Alfred Fuller
wrote:
> Yes, the write ops for changing an entity depen
Yes, the write ops for changing an entity depends on how many indexed
properties you change. It is:
1 op for the entity
2 ops for each changed index value (1 to remove the old value and 1 to add
the new)
Since it is not a fixed value and depends on what you actually modify, we do
not (can not) sho
So the Write Ops value in the new dev_appserver's Datastore Viewer
applies only to creating new entities of a kind, updating the entity i
is presumably much cheaper if only a few properties are changed?
On Tue, Sep 20, 2011 at 12:27 PM, Simon Knott wrote:
> Hi,
>
> According to Alfred, who's a Go
Thanks for bringing up that.
Indexes updated are property changed related.
I think that clears alex question. ;)
FYI, if you have properties you will never filter or sort on in a query,
consider *indexed=False* to avoid this write ops
Best,
Jose
--
You received this message because you are s
Hi,
According to Alfred, who's a Googler who appears to know lots about the
datastore, only the updated values cause index write operations - see
https://groups.google.com/d/msg/google-appengine/mjnSqQWOfqU/cgPVeHbrR8oJ
for more info.
--
You received this message because you are subscribed to
Hi,
AFAIK, when you do a put() it will update the hole entity. that been said it
will also update all the indexes related to it.
Hope this helps!
Jose Montes de Oca
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To view this discussion
