On Tue, Dec 8, 2009 at 1:26 AM, Toby tobias.ro...@sunnymail.mobi wrote:
Reading the doc carefully it tells me that indexes are created based
on the queries I make. Hence if I never query an entity on a certain
property there should be no index.
That's not exactly what it says. Only the
On Mon, Dec 7, 2009 at 2:20 AM, Toby tobias.ro...@sunnymail.mobi wrote:
thank you for your update. In fact I was suspecting the index or other
management data. But it is hard to believe that it leads to such a big
overhead. I mean it is enormous to have an index that is 10 times more
than the
On Mon, Dec 7, 2009 at 5:42 AM, SCMSoft scms...@gmail.com wrote:
We always used to have ~100ms api cpu_ms, but cpu_ms used to be more
like 50ms or so. We added logging on the time of entry and exit of
doGet() and there was 58 ms difference in this case. How is it
possible to have 210cpu_ms,
On Sat, Dec 5, 2009 at 9:29 AM, Toby tobias.ro...@sunnymail.mobi wrote:
I know that they are updated at least once a day. In my case the data
volume has not changed for quite some time. And the discrepancy is
really huge. I mean 50MB to 500MB. So maybe my datastore contains
stuff that does not
On Sat, Dec 5, 2009 at 10:05 AM, Eric Rannaud eric.rann...@gmail.com wrote:
They also talked about an article they will publish soon that gives
enough details on how indexes are built that you can at least predict
the size of your indexes.
There it is:
http://code.google.com/appengine/articles
