I think all of you except Micheal missed the point of the question. I hate when this happens to me :)
Of course it's impossible to store 1 million integers in a list property, however, I think in the question, 1million was more like an N and the point of the question is to whether any update to the repeated list, causes O(N), index operations, therefore: If one adds N elements to a list_property, put (save) the list property after each addition, are there O(N) index operations or O(N^2) [at total] And why are repeated properties slow, I also use them for tags and stuff, maximum 20 elements in each of them, and sometimes wonder, what happens when I assign a repeated property that has [1,2,3] to [1,2,3,4] (not adding an element, but rather than that re-setting the array with a new element) On Friday, January 25, 2013 9:37:29 PM UTC+2, Ryan Chazen wrote: > > Depends if those integers are indexed or not. Each index is a write op. > However, an entity can only be 1mb big.. I think 1 million integers would > be more than 1mb as appengine stores natively as strings... > > What you could try is to store the integers in multiple entities (say > 1-1000 integers per entity). That would make adding new integers easy as > you would not need to modify old entities. You could join all the integers > back together if needed with a query. > > On Friday, January 25, 2013 8:32:48 PM UTC+2, Jiansen He wrote: >> >> Hi, >> >> Say an entity has a list property which has 1 million integers. Now we >> need to update the list property by adding 1 more integer. Does updating >> via put cost 2 million write operations? If so, is there a cheap >> alternative? >> >> With Thanks >> Jiansen >> > -- 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]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
