Does read/write an entity with arraylist cost more than an entity w/o arraylist

[Qingshan Bie]

Hi GAE Datastore experts,

I have a question about cost of read/write an entity from/to GAE datastore. Say, I have two type of similar entities, one with arraylist as its field and the other does not. If I need to read the arraylist and make changes and write again to datastore, do they cost the same (datastore operations) or the one with arraylist cost significant more?

Please help.

Thanks,
Bendanpa

[nischalshetty]

I am not an expert but this is what I believe I know :

• If it is an unindexed field then it should not be a problem
• If it is indexed, then yes, it would be more expensive

However, even I would like to know how expensive the writes are for Lists. Does it matter if the list has 5 objects or 500 objects?

[Bendanpa]

My case is unindexed. I also want to know if it matters with the size of the list. Anyone please help

Thanks,
Bendanpa

[Ikai Lan (Google)]

They cost the same.

The new SDK should show you how many datastore ops things are taking:

http://www.iclarified.com/entry/index.php?enid=2984

--

Ikai Lan 
Developer Programs Engineer, Google App Engine

plus.ikailan.com | twitter.com/ikai

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/h7UGRA4hVG4J.

To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Jeff Schnitzer]

In a related question, if we get() + put() an existing entity with
indexed fields, and those field values have not changed, are we
charged for updating the indexes again?

Jeff

[Jason Collins]

Hi Jeff,

A post from Alfred Fuller on this thread:
http://groups.google.com/group/google-appengine/browse_thread/thread/9a39d2a9058e7ea5/d8d3a2bfa2c6b8aa?lnk=gst
suggests, no, you don't pay unless the indexes have changed.

Though note that you pay "double" for those that have changed: the old
must be deleted, and the new must be written.

j

On Sep 15, 11:43 am, Jeff Schnitzer <j...@infohazard.org> wrote:
> In a related question, if we get() + put() an existing entity with
> indexed fields, and those field values have not changed, are we
> charged for updating the indexes again?
>
> Jeff
>
> On Thu, Sep 15, 2011 at 10:33 AM, Ikai Lan (Google) <ika...@google.com> wrote:
>
>
>
>
>
>
>
> > They cost the same.
> > The new SDK should show you how many datastore ops things are taking:
> >http://www.iclarified.com/entry/index.php?enid=2984
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Engine
> > plus.ikailan.com | twitter.com/ikai
>

[Jeff Schnitzer]

Thanks - this is what I was expecting/hoping.

It would be nice to have finer-grained control over indexing... ie
just ascending index, or no single-property indexes required for
composite index.

Jeff

[Jason Collins]

I couldn't agree more.
j

On Sep 15, 2:06 pm, Jeff Schnitzer <j...@infohazard.org> wrote:
> Thanks - this is what I was expecting/hoping.
>
> It would be nice to have finer-grained control over indexing... ie
> just ascending index, or no single-property indexes required for
> composite index.
>
> Jeff
>
> On Thu, Sep 15, 2011 at 12:23 PM, Jason Collins
>
>
>
>
>
>
>
> <jason.a.coll...@gmail.com> wrote:
> > Hi Jeff,
>
> > A post from Alfred Fuller on this thread:

> >http://groups.google.com/group/google-appengine/browse_thread/thread/...