Hi Marzia,

Just want to add my voice to the chorus of people looking for a little
more transparency in terms of data storage and entities.  In my ideal
fantasy world I'd be able to see a pie chart that would break down the
percentage of storage that each of my entities was using as a fraction
of the total storage used.  Clicking on an entity's slice in the pie
would bring up another pie chart that would show the fraction of
storage used by that entity's primary store and each of its indices.
(This second chart may not be necessary once you guys have published
some more info on exactly how different properties and indices
manifest themselves on disk.)

Thanks in advance,
Ben



On Mar 13, 9:57 am, Marzia Niccolai <ma...@google.com> wrote:
> Hi,
>
> There is no 'multiplier' per se on datastore storage.  The issue is that we
> account for both the size of the data stored and the space taken by the
> indices for this data.  As such, the amount of storage you use depends
> specifically on the types of indexes your application has.
>
> We are working on getting better documentation together that will give you a
> good idea on how you can account for the amount of storage an entity will
> take.
>
> Please note that the FAQ on this subject currently is _not_ correct and we
> will be updating it.
>
> -Marzia
>
> On Tue, Mar 10, 2009 at 9:28 AM, Jonathan Ultis 
> <jonathan.ul...@gmail.com>wrote:
>
>
>
>
>
> > I created a model with fixed content that requires ~250b serialized,
> > including all field names, the key, and the kind name, and parent
> > (None). I added 312000 of those to the datastore, for 75 megs of raw
> > data. There are 8 indexable fields, The indices should require no more
> > than 176 megs of additional space, if the indices don't do any sort of
> > column compression. That's 250 megs of raw space.
>
> > But, the data store reports 1GB of space used.
>
> > That suggests perhaps 2x redundancy, plus a 50% fill rate in big
> > table. Or, maybe just 4x redundancy. No idea.
>
> > Anyhow, for now, take your raw object size including kind, key, field
> > names, and field content, and multiply by 10x-15x, depending on how
> > many indexable properties you have, to get your final storage size.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to