I think it is a great ide. Would certainly help us better understand
how we are using space.
Robert
On Tue, Feb 9, 2010 at 4:12 AM, Pavel Kaplin wrote:
> I like this suggestion too. Moreover, I'd prefer detailed description of the
> number called Used Space on Dashboard/Quota Details pages
I like this suggestion too. Moreover, I'd prefer detailed description of the
number called Used Space on Dashboard/Quota Details pages. E.g. indexes =
250 Mb , Entities = 500 Mb, sessions = 50 Mb and so on, plus detailed info
about indexes and sessions. What do you think?
On Mon, Feb 8, 2010 at 9:
No, I don't store any info in sessions, except logged in user id via Google
Users API.
On Mon, Feb 8, 2010 at 8:48 PM, Ikai L (Google) wrote:
> Are you storing information in sessions? Session information can also take
> up space.
>
>
> On Mon, Feb 8, 2010 at 5:32 AM, Pavel Kaplin wrote:
>
>> He
I like Philip's suggestion a lot. It will help us all identify space
intensive indexes, and _hopefully_ reduce the number of posts about
this.
I submitted a feature request for this issue:
http://code.google.com/p/googleappengine/issues/detail?id=2740
Robert
On Mon, Feb 8, 2010 at 2:27 PM, W
This issue comes up about once per week. Google -- you need to address
this. The simplest way of addressing it would be to put the size of
*every* index on the statistics page, and show that the total
corresponds (roughly) to the quota number.
This would enable people to see which index (or indexe
Are you storing information in sessions? Session information can also take
up space.
On Mon, Feb 8, 2010 at 5:32 AM, Pavel Kaplin wrote:
> Here's the detailed description of mentioned indexes:
> 1) address (string, < 100 bytes), tradePoint(String, < 100 bytes),
> user (Key, generated by GAE), t
Here's the detailed description of mentioned indexes:
1) address (string, < 100 bytes), tradePoint(String, < 100 bytes),
user (Key, generated by GAE), timestamp
2) tradePoint, user, timestamp
3) user, timestamp
Entities count is about 15k. I don't understand how it might happened.
On Feb 8, 3:
Hi Pavel,
That depends on the nature of your indexes, and the entities being indexed.
It's certainly possible for indexes to reach this magnitude - particularly
if you're indexing list properties.
-Nick Johnson
On Mon, Feb 8, 2010 at 1:12 PM, Pavel Kaplin wrote:
> It's hard to believe that 3 i
It's hard to believe that 3 indexes (for 2, 3 and 4 fields) could eat
9x more space than data itself.
On Feb 8, 2:45 pm, "Nick Johnson (Google)"
wrote:
> Hi Pavel,
>
> The datastore stats include only the raw size of the entities. The total
> space consumed is the space consumed by the entities,
