|How I reduced my AppEngine costs despite new pricing||Santiago Lema||9/1/11 9:06 AM|
I detailed on my blog how using simplificative optimization can
compensate for the unbelievable price increase. As you can see there
wasn't any good reason to worry.
As usual we developers were stupid and Google in its almighty goodness
was just misunderstood. Adapting the code appropriately will
definitely lower our bills.
PS: Sorry. I had to.
|Re: How I reduced my AppEngine costs despite new pricing||Angke||9/1/11 10:37 AM|
OMG great post!
|Re: How I reduced my AppEngine costs despite new pricing||Jon Romero Vlachogiannis||9/1/11 1:40 PM|
I have written a post that actually worked for us:
|Re: How I reduced my AppEngine costs despite new pricing||Santiago Lema||9/1/11 3:14 PM|
Joke aside removing "always on" instances (that were sitting idle) and
upping the latency a bit to 60ms did move my public website
(smallte.ch) from a ridiculous 6 instances to between 1 and 2,
effectively making it acceptable.
When it comes to my iPhone stats websites it seemed to reduce the
number of instances slightly but still the price to pay is huge
compared to the service given. The price for one instance is just
ridiculous. It's just as expensive as a dedicated server. And you
still have to pay additional bandwidth and storage.