Very interesting, thanks for sharing. If you just need a simple dictionary-like storage, why not just repr() and eval() - wouldn't that be even faster?
On Jul 13, 8:05 am, someone1 <[email protected]> wrote: > I just looked into this myself. Best bet is to use a Text or Blob > property to store in a JSON format: > > http://kovshenin.com/archives/pickle-vs-json-which-is-faster/ > > I did many tests with 250-500 expando properties and the results were > horrendous. From digging around I didn't find a way to disable > indexing expando properties, and this made writing them very > expensive. > > On Jul 13, 1:35 am, Pol <[email protected]> wrote: > > > > > > > > > Hi, > > > Regarding expando properties: > > > 1) Can you prevent them from being indexed (I couldn't find anything > > about this, but I'd like official confirmation)? > > > 2) What's the practical number of expando properties you shouldn't go > > above? If they are all indexed, then surely that can be quite > > expensive, so you should stay below 100 or something? > > > 3) If you have to be above the limit defined at #2, what's the best > > alternative? Serializing into a blob property, possibly, but what > > would be the most optimal serialization format? > > > Thanks! -- 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.
