Hi Matija, I would do some testing and benchmarks for your intended application to confirm, but they should be more-or-less comparable.
In the first case (multiple single valued props) you wind up with 12 index rows based on the properties, plus the 5 custom index rows. In the second case (one single valued prop, one multiple valued prop) you'll have 12 index rows based on the two properties, plus the 5 custom index rows. So, unless I've misunderstood your model defs, they will result in a very similar amount of work. One possibly important difference, the fist method is going to use a few more of the indexes you're allowed. So If you have a lot of kinds you run queries needing indexes on, that could be a factor. Robert On Thu, Dec 30, 2010 at 05:06, Matija <[email protected]> wrote: > What entity will have faster index creation (smaller cpu api ms) ? > Entity with six single valued properties and five custom indexes (two > properties indexes, first property and each of other five properties) or > entity with one single valued property, one multivalued property (five > members) and one custom index (two properties index, where second property > is that multivalued property). > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
