On Wed, Mar 5, 2014 at 2:55 AM, Mattan Furst <[email protected]> wrote:
> I have a situation where I have an entity with several tidbits of > information that I need to save (currently around 20-30 columns each with a > few bytes of information worth). Most of those tidbits do not require > indexing. It used to be that I would save every piece of information in a > different indexed column. After reading up on the subjects I came to > realize that I can save costs and performance by not having all the pieces > of information in indexed column. I have 3 main options I consider changing > into: > 1. Keep saving the various column I don't need indexing for but turn their > type to ByteString to keep them from being indexed. > 2. Get all the tidbits of information, turns them into some common format > like json or xml and store that in a single blob column. > 3. Same thing as 2 but before storing the blob compress it using some fast > and common compression algorithm like. > > Which is the better option? > > As Chad noted, it depends on your runtime and whether you're using the low level API or some sort of abstraction layer. If you're using the low level API, there's a way to set certain properties as unindexed (you don't need to do any conversion). This way is probably the easiest and fastest way. You can also convert to JSON or XML, but that involves a lot more work (writing a conversion script, testing, etc). It's much more straightforward to simply set the columns as unindexed. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
