Argh! This means that one form (db.Key) is smaller than the other (comparable string) for the datastore while the reverse is true for memcache.
I've created am issue ( http://code.google.com/p/googleappengine/issues/detail?id=1538 )requesting a __getstate__ and __setstate__ for db.Key that is smaller than the string equivalent. In addition to eliminating the inconsistency betwen the datastore and memcache sizes, it will reduce the size of every memcache'd db.Model instance whose .key() is defined. On May 13, 11:41 am, "Jason (Google)" <[email protected]> wrote: > Hi Andy. In this case, the list of Key objects will be smaller than the list > of key strings. Even though the picked db.Key object is larger, it is a > binary-encoded protocol buffer form that gets stored, which is smaller than > the pickled string. That said, I doubt it would make a tremendous difference > unless you have a lot of these entities or these lists have a lot of values. > > - Jason > > > > On Mon, May 11, 2009 at 10:38 PM, Andy Freeman <[email protected]> wrote: > > > Since index space can be significant, can we get some additional > > information? > > > For example, does an indexed db.ListProperty(db.Key) with three > > elements take significantly more or less space than an indexed > > db.StringListProperty with three elements whose value is str() of the > > same keys? (The pickle of keys seems to be significantly larger than > > the pickle of the equivalent strings.) > > > On May 11, 5:04 pm, "Jason (Google)" <[email protected]> wrote: > > > Hi Anthony. I'm very sorry for the late reply, and thank you for bearing > > > with me. I've discussed this with the datastore team and it's evident > > that > > > the CSV file's size is not a great indicator of how much storage your > > > entities will consume. On top of the size of the raw data, each entity > > has > > > associated metadata, as you've already mentioned, but I'd bet that the > > > indexes are consuming the greatest space. If you don't ever query on one > > or > > > more of these 15 string properties, you may consider changing their > > property > > > types to Text or declaring indexed=false in your model. If you can do > > this > > > with one of your properties and re-build your indexes, I'd be interested > > in > > > seeing how much your storage usage decreases since you'll need one less > > > index. > > > > (Note that single-property indexes are present but not listed in the > > Admin > > > Console.) > > > > - Jason > > > > On Sat, May 9, 2009 at 4:34 PM, Kugutsumen <[email protected]> wrote: > > > > > Two weeks ago, I've sent my applications ID to both you and Nick and I > > > > haven't heard from you since then. > > > > > Thanks- Hide quoted text - > > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
