On Tue, Oct 20, 2009 at 2:26 PM, Alexander Arendar <
alexander.aren...@gmail.com> wrote:

>
> Does it mean that indexing overhead like you call this is about 500
> times...?
>

That depends entirely on what you're indexing and what indexes you have. An
exploding index, for example, can easily result in at least this level of
blow-up.

-Nick Johnson


>
> On Oct 20, 3:43 pm, "Nick Johnson (Google)" <nick.john...@google.com>
> wrote:
> > Hi,
> > The difference you're seeing is due to indexing overhead. Removing
> composite
> > indexes and setting fields as indexed=False will substantially reduce
> your
> > index consumption.
> >
> > -Nick Johnson
> >
> >
> >
> > On Sat, Oct 17, 2009 at 5:49 AM, _RT_ <r...@daparty.ru> wrote:
> >
> > > I have a simple application that stores some records (4 integer
> > > fields). For now it's over 40k records in datastore.
> >
> > > Datastore statistic says:
> >
> > > Last updated    Total number of entities        Size of all entities
> > > 3:17:33 ago     41,800  4 MBytes
> >
> > > But in dashboard I seeing:
> >
> > > Stored Data      $0.005/GByte-day                0%      2.41 of 801.00
> > > GBytes   $0.01 /
> > > $4.00
> >
> > > So, what happen? It's so bad, because I need store 3,5 million records
> > > (with this trend it's over . How can I reduce Stored Data resource?
> >
> > --
> > Nick Johnson, Developer Programs Engineer, App Engine
> > Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration
> Number:
> > 368047
> >
>


-- 
Nick Johnson, Developer Programs Engineer, App Engine
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 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