Hi Jeff,
Yes, it's really a concern. Previously fetching 20 small sequential
entities cost about the same as fetching 1 large entity 20x the size of the
small ones. Now it's costing 10-20x as much because of the per-read (and
per write for puts) pricing.
I'm already using memcache extensivel
The first question I would ask is: Is this really a problem? Have
you looked at your bill and decided for certain that the savings would
be worth changing your code & possibly cluttering your business logic?
That said, I would be tempted to see what optimization you can make
with memcache. Seem
I'm looking for some opinions on to what degree I should aggregate my now
small entities together into larger entities. Presently I have 50,000 "Day"
entities where each entity is represents a day.
They are relatively small with 6 float, 2 bool, 1 int, and 1 string
property. No property index
