Not sure how you're getting the 2x fps sensation. On a 4S, using the OpenGL ES analyzer in Instruments while browsing similar neighborhoods at similar zoom levels, I average ~35fps in Google Maps and ~55 in Apple Maps.

Not terribly surprising though - Apple Maps would have access to all the private APIs that AppStore apps can't use.

I've been playing with it for about an hour - and I think one of the interesting tricks that the Google Maps plays is that, in addition to making aggressive use of cacheing (which the IOS 6 map application does as well) - The Google Maps displays low-resolution version of the map you are moving into, before display the high res. The IOS 6 Maps app tends to display a blank background, so you may be more aware that the entire map hasn't been displayed.

It will be interesting to see if there is any server impact, as millions of people start using this Map Application tomorrow. (In both directions - it may be the case that the Apple Map servers will see a drop in use, and increase in performance)

It seems that he is talking about how fast new map data/tiles download and display when you are scrolling/zooming the map.

It is a swipe in, but on the tutorial overlay its referred to as a tap.

Weird. Google Maps feels about 2x slower to me. Especially when turning the map.

I have a 3Gs running 5.1 and the new version is much slower than the original. I'd guess about about 5FPS, and 2-3x slower. This app needs some performance optimization.