Ok. So I've changed the entities to use entity.setUnindexedProperty().
To get rid of the superfluous the indices I'm doing something like
this:
Query q = new Query(PlayerSnapshot.class.getName());
ListEntity asList =
ds.prepare(q).asList(FetchOptions.Builder.withLimit(n).offset(o));
Hello!
I've been experimenting with GAE for a couple of weeks. My project is
a leaderboard java/js app for an online game. It's currently backed by
~200k data point entities that should use 200 mb of storage.
The datastore statistics tab reports that size of all entities (153k)
is 105mb. I have
Hi Erik,
There are several things that can eat into your stored-data quota.
Did you explicitly disable indexes on all of your properties except
the timestamp? If not you have two indexes on each property. Indexes
can easily double your stored data size. If you'd like to see index
stats,
Hi Erik,
Can you post the definition for one of your entities? I look at look at your
dashboard, and here's what I see:
- 105mb used by datastore entities
- 0 tasks using task queue stored bytes quota
- 0 blobstore bytes used
- 1 COMPOSITE index
Note that built-index indices also consume
Hey guys!
This seems to be exactly what's happening. I'll take a look at it
tomorrow when I'm, ehrm, back in the game (happy birthday to me! :)
I have 17 props/entity, so if GAE started to implicitly index the the
quota makes sense. (code is available on
Hi Erik,
If you mark them as unindexed, new entities will not be indexed,
but you'll have to re-put your existing data to clear up the space.
Robert
On Tue, Feb 8, 2011 at 16:54, Erik Lindblad erik.lindb...@gmail.com wrote:
Hey guys!
This seems to be exactly what's happening. I'll
