On App Engine, what does optimization for reads mean?
Posted
by Honza Pokorny
on Stack Overflow
See other posts from Stack Overflow
or by Honza Pokorny
Published on 2010-04-22T21:11:48Z
Indexed on
2010/04/22
21:13 UTC
Read the original article
Hit count: 259
python
|google-app-engine
In the documentation for Google App Engine, it says that when designing data models for the datastore, you should "optimize for reads, not writes". What exactly does this mean? What is more 'expensive', CPU intensive or time consuming?
© Stack Overflow or respective owner