Hi Kyle Yes I am using it and have been seeing a slight decrease in CPU consuption following the addition of indexed=False to around 15 string propertytypes and 3 list propertytypes in my two main model. It has reduced the load around 100ms or 12% or so.
However, I must note that I have no way of actually "scientifically" monitoring this, other than really just looking at the average load before and after. It could also just be that the App Engine servers are running a little more smoothly. But I choose to believe that it at least had some effect. However, make sure you do not indexed=false ANY properties that you want to filter or sort on later, as this will ruin the backward- compatibility of your datastore model. Best, T On May 10, 4:19 pm, Kyle Jensen <[email protected]> wrote: > I have some models with many properties; however, I need indexes on > only a handful. I noticed the new sdk supports > "indexed=False":http://code.google.com/p/googleappengine/wiki/SdkReleaseNotes > > Is anybody using "indexed=False" on properties? Is there a noticeable > benefit? > > Sincerely, > Kyle --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
