3. You must store built-in and custom index rows that refer to the
entity. Each row contains the kind (type) and a collection of
property values for the index definition.
Data Sent to / Received from the API : Just like it sounds, App Engine
measures how much data is requested from the datastore when
retrieving entities or performing queries and how much data is sent
to the datastore when creating or updating entities or performing
Datastore CPU Time : This measurement also counts toward your
CPU time quota. But with respect to datastore operations, CPU
time is measured separately as well. It's calculated and
summarized using the same benchmark 1.2GHz CPU.
The datastore has some unique issues related to indexing, which is a more
advanced topic. Datastore indexes do count against your application's storage quota.
Table 2-4 shows which data is stored for various indexes to help you estimate how
much your indexes are consuming.
Table 2-4. Datastore for Indexes
Data per Row
Kind - querying
entities by type
One row per entity
Application ID, kind,
primary key, small
Property - querying
entities using a single
One row per property value
per entity. Db.Blog and db.Text
value types are excluded.
ListProperty properties will
return one row per value in
Application ID, property
name, property value,
Composite - querying
entities using multiple
One row per unique
combination of property
values per entity
Application ID, value1,
value2,… where value* is
a unique combination of
values of properties in
the composite index