I don't think I've posted here before, but I've been an appengine user
for a while now (closing on 2 years? Is that even possible?). And like
many, I had a rude shock with the new pricing (going from $0.50/day to
$50/day).
However, I dug into what I'm actually being charged for, and I think
it's all actually in my control to sort out, and that in itself is
sort of fascinating. I wrote a long blog post on this, which people
might find interesting.
The Amazing Story Of Appengine And The Two Orders Of Magnitude
http://point7.wordpress.com/2011/09/03/the-amazing-story-of-appengine-and-the-two-orders-of-magnitude/
I'd be really grateful for feedback, especially if I've gotten
anything wildly wrong. I haven't actually made any of the changes that
I've foreshadowed in the post, that's for the next day or two, and
I'll write a followup article on how it goes.
Thanks in advance for having a look!
--
Emlyn
http://my.syyn.cc - Synchonise Google+, Facebook, WordPress and Google
Buzz posts,
comments and all.
http://point7.wordpress.com - My blog
Find me on Facebook and Buzz
I think a lot of people just need to take a deep breath and look at their apps the way you did. It's certainly a lot less work than migrating to EC2.
> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
THAT is a fantastic idea.
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/qa8mqxfJ25MJ.
I totally agree with you! I don't clearly remember writing that bit of
code, but it looks like a kludgy workaround for a bug. This app is an
evenings & weekends thing, so "what can I do in 10 mins to fix
critical issue X" is often the driving factor. That doesn't lead to
good code ;-)
> like the one you found, are conspiring to make a lot of these crazy new billing numbers.
I think that's going to end up being true. What Google are doing with
the new billing is surfacing the true costs of the platform, which
were hidden before. It's pain we've got to go through, and it'll be
better for all of us in the long run. That said, it would have been
nice to have had a little longer between getting access to the new
billing tools and actually wearing the new costs. But it does focus
the mind!
>
> I think a lot of people just need to take a deep breath and look at their apps the way you did. It's certainly a lot less work than migrating to EC2.
Absolutely. We need to not lose sight of just how great a PAAS
platform this is, and how much we gain by using it.
--
Emlyn
http://my.syyn.cc - Synchonise Google+, Facebook, WordPress and Google
Buzz posts,
comments and all.
http://point7.wordpress.com - My blog
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/ZgT491lCdLUJ.
Well,.. I intentionally tried to make a suggestion that requires as little deviation from the existing plan as possible. I have no faith in GAE team making anything but baby steps towards the community -- that request in the linked ticket is way too ambitious.-Sergey
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/TIcQn3mpRLgJ.
http://point7.wordpress.com/2011/09/04/appengine-tuning-1/
Which leads to a potential constructive suggestion. Maybe Goog can
post a troubleshooting guide that lists different line-items in the
new-style billing, and potential gotchas? An example in your blog is
that sudden parallelism is costly and that making things serial is a
good optimization. (Ironically, the opposite of what was being
promoted earlier - mapreduce). Another factoid is that offset queries
are costly. Using queries as a generator is costly, and you should
fetch items at once.
So it can look like this:
Excessive instances cost? Look at these items:
- sudden parallelism
- idle instance setting
- decrease response time
- other?
Excessive writes:
- decrease unneeded indexes
-
Excessive Reads:
- make sure your fetch() rather than looping through results
- check offset queries
- etc...
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
On Sat, Sep 3, 2011 at 8:23 AM, johnP <jo...@thinkwave.com> wrote:
Which leads to a potential constructive suggestion. Maybe Goog can
post a troubleshooting guide that lists different line-items in the
new-style billing, and potential gotchas? An example in your blog is
that sudden parallelism is costly and that making things serial is a
good optimization. (Ironically, the opposite of what was being
promoted earlier - mapreduce). Another factoid is that offset queries
are costly. Using queries as a generator is costly, and you should
fetch items at once.
So it can look like this:
Excessive instances cost? Look at these items:
- sudden parallelism
- idle instance setting
- decrease response time
- other?
Excessive writes:
- decrease unneeded indexes
-
Excessive Reads:
- make sure your fetch() rather than looping through resultsIf you look or use fetch the cost is the same (though fetch might be faster as it will pick larger batch sizes)
http://point7.wordpress.com/2011/09/03/the-amazing-story-of-appengine-and-the-two-orders-of-magnitude/
http://point7.wordpress.com/2011/09/04/appengine-tuning-1/
http://point7.wordpress.com/2011/09/07/appengine-tuning-an-instance-of-success/
http://point7.wordpress.com/2011/09/10/appengine-tuning-schlemiel-youre-fired/
tl;dr is, that my pricing's back down really low, things have worked out.
btw I've had great feedback, tips and techniques from this community.
Thanks! I think that, regarding longevity of a tech, the culture that
builds around a it is just as important as the tech itself. All signs
are that AppEngine is going to be a long term viable platform.
On 3 September 2011 19:46, Emlyn <emlyn...@gmail.com> wrote:
So optimisation is even easier than I thought. Gerald, I'll quote you
in an update to my post, if you're ok with that.
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/dWoTZKzCy7kJ.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
--
cool
Oh, I don't need to visit all the monitors, far from it. It's just a
bit of crap code doing that which needs to be refactored out entirely.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/3QXRW2UJcB8J.