[google-appengine] Re: Cost of updating list property

2013-01-25 Thread Ryan Chazen
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

[google-appengine] Re: Cost of updating list property

2013-01-25 Thread Michael Hermus
I believe that each value in an indexed multi-valued property gets its own index entry. Therefore, I think that adding 1 value should incur the cost of adding one index entry, which is 2 writes (one for asc, one for desc) and 1 write for each custom index that includes the property. -- You rec

[google-appengine] Re: Cost of updating list property

2013-01-25 Thread Kaan Soral
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

Re: [google-appengine] Re: Cost of updating list property

2013-01-25 Thread Guido van Rossum
The only way to get this to perform is to serialize the values into a string. Repeated properties are way too slow when you get to this number of repetitions. (They're good for tags, which need to be indexed, and of which youd expect there to be z few, or dozens, or occasionally hundreds.) --Guido