You dont really give any indication of the project you need to be 'fast' so sorry if i under-estimate your skill, but just as a reminder to anyone starting out...
Unless your webapp (and it is a webapp, otherwise you would not pick appengine, right?) is **REALLY** heavy in need for CPU, programming language probably does not matter to the final speed.
As you can see, any time you have to use the network or hit the disk then CPU is no longer your bottle neck. Check out the 'scaled to 1 CPU cycle == 1 second' times to get some appreciation of just how slow any external data access really is.
My suggestion is always program in the easiest language to code in to get your project working with the least possible bugs. Then test and revisit the code.
You can go back and optimise the speed *after* it works correctly. For example, Id always pick python over c++ for any web project just because you can probably get the task done in 20 lines rather than 200 and in about 1/10th of the time in python. Ive seen too many starting programmers choose C++ because 'it is fast' when they just need to do simple operations that you could code n 10 lines in a scripting language.
Note this does not apply if you *REALLY* need the CPU, for example if you need to take some values in and generate 10000x10000 pixel Mandelbrot sets or something, but for 99.9% of webapps the programming language will make almost no difference to page compute speed.
IMHO, #include <disclaimer.h>, etc etc...
cam