Hi jgilfelt, On Thu, Jul 9, 2009 at 10:47 AM, jgilfelt<[email protected]> wrote: > > Hi Nick, > > Thanks for the info. > > No, the index had been in place for some time. I was initially working > with a small set of test data (15k entities) and my usage was around > the 10% mark. Within the last week or so I started uploading my full > data set via the remote_api data uploader and saw only incremental > usage changes, peaking at 20% with 100k entities. Two days later I saw > the jump to 96%. > > Is there normally a delay with the dashboard reflecting the "true" > datastore usage (with respect to indexes and other overheads)?
Yes - the actual usage is typically updated once a day, with usage in between being an estimate of actual usage. Charging is based only on actual usage. > > I am happy to purchase additional quota, but I think we need a clearer > picture of application datastore usage. Perhaps the dashboard could be > enhanced to include the size of specific indexes? We're working on improving the visibility of datastore usage. -Nick Johnson > > Jeff. > > > On Jul 9, 10:06 am, "Nick Johnson (Google)" <[email protected]> > wrote: >> Hi jgilfelt, >> >> Does the jump in space usage roughly coincide with the creation of the >> index you describe? You should expect a large blowup in data size due >> to both built-in and custom indexes, especially indexes on a list, >> which will create one index entry per list item. For 100,000 entities >> to use your 1GB of built in quota is not difficult - about 10k per >> entity after all indexing and storage overhead. >> >> -Nick Johnson >> >> >> >> On Wed, Jul 8, 2009 at 10:12 PM, jgilfelt<[email protected]> wrote: >> >> > In the last day or so, the app I am developing has seen a sudden jump >> > from 20% to 96% of the free quota for stored data for no apparent >> > reason. The raw data that I have uploaded via remote_api is less than >> > 60 megabytes in size and about 100,000 entities. >> >> > Not sure if the problem is index related or not. I do have an index on >> > a multi-value list property and two booleans. I understand that this >> > will incur storage overhead, but it is necessitated by the need to do >> > "bounding box" geo-spatial queries within the application. The index >> > itself shows a status of "Serving". >> >> > Can anyone shed any light on the reason for such a data usage >> > increase, and whether or not it is legitimate or some sort of anomaly. >> >> > My app id is on-location. >> >> > Thanks, >> > Jeff >> >> -- >> Nick Johnson, App Engine Developer Programs Engineer >> Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration >> Number: 368047 > > > > -- Nick Johnson, App Engine Developer Programs Engineer Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
