Vacuuming just applies to your configured indexes not the single-property indexes themselves. There was a post recently about possibly making it more obvious somewhere in the dataviewer which properties are indexed and which aren't because people can start off with something indexed then unindex that property (or vice versa) and they think it applies to all existing properties but it doesn't. You have to run throw them all and unindex (or index) existing entities.
Yes it would be nice if were broken out a little better as two what is included in the total usage like task queue storage, etc. Also, watch out for those long property names, depending on the number of entities, all of it can add up. On Thu, May 19, 2011 at 10:47 AM, Brandon Wirtz <[email protected]> wrote: > I think I went out of my way to use non-indexable types, but I'll make sure > that is the case. I often store things as type blob to prevent indexing. > But I may have set some things to the wrong type. > > You don't think Vacuuming would help with this? > > Considering all the other data shown in Quota Details it would be nice if > Google exposed this. > > Thanks for the help I appreciated it both times. > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Stephen Johnson > Sent: Thursday, May 19, 2011 10:42 AM > To: [email protected] > Subject: Re: [google-appengine] Still confused about Storage reported for > billing and Datastore > > Hi Brandon, > Different Steve here. Anyway, when I mentioned in a different thread about > indexes, you also have to count your property indexes as well. > For each property that you have indexed (and these wouldn't show up in your > configured indexes) you have two indexes defined: one ascending and one > descending. If these properties have large amounts of data, for example, > string/text data then it is copied to those indexes as well as the keys so > if you have very long key values then it is in those indexes. Also, if you > have long property names those are copied over and over again with each > piece of data. In a different thread I posted some general guidelines that > help to keep these numbers low. > Steve > > On Thu, May 19, 2011 at 9:02 AM, Brandon Wirtz <[email protected]> wrote: >> Yes, Yes, Yes. >> >> $9 was the amount of Mt. Dew Per day, not per month. Currently it's >> across >> 10 apps, but in the next month it is across 15k domains. Rounding >> Errors could pay for another 3 interns at that scale. >> >> Also because the number seems to be so close to 2.5:1 I wonder if this >> is a bug. I don't mind paying if that is the pricing. >> >> Really All I am looking for is, is it accurate, and if so where is the >> other storage being used, and do I have control over it. I reduced >> my bill about 60% last week through re-writing my code, and adding >> better caching and memory management. If I can find another 10% that goes > to my bottom line. >> So Capitalism is driving my innovation. >> >> >> >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Stephen >> Sent: Thursday, May 19, 2011 5:37 AM >> To: [email protected] >> Subject: Re: [google-appengine] Still confused about Storage reported >> for billing and Datastore >> >> On Thu, May 19, 2011 at 8:36 AM, Brandon Wirtz <[email protected]> > wrote: >>> >>> I still have 2.5x as much billed usage for HR Storage as I have >>> reported by the datastore admin. >>> ... >>> It's only 10 cents a day on most my apps, but that's $3 a month. (per >>> app) which isn't a big deal yet, but it adds up across lots of apps. >> >> That's less than you spend on Mountain Dew each month. >> >> Have you tried putting Ad Sense on these pages? >> >> This aint no hippy commune. This is capitalism and that's what drives >> innovation. >> >>> I don't mind if I'm really using it... >> >> Interesting perspective - "Pay for only for what you use", as Amazon >> would say. >> >> :-) >> >> -- >> 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. >> >> >> -- >> 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. >> >> > > -- > 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. > > > -- > 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. > > -- 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.
