Since v2.118, I applied elapsed time between the request of GMap API
loader js and the firing of infowindowopen event on the frame-based
test page below, and I've been monitoring the performance of v2.x and
v2 against v2.118 (pre-modularization of GInfoWindow).
http://genes.com/maps/gmap_test.htm
I pay a lot of attention to the quickness of the bubble display
because usually important info are contained in this, and speeding
this up enhances user experience. And, it is very significant for some
mobile devices especially those with javascript execution time
limitation.
The site will load test pages with different versions of the API
loader into an iframe by clicking on the radio buttons. The actual
version number and the elapsed time will be shown in the infowindow
and recorded on the left panel.
It also checks if the issues of content overflowing and the limitation
of infowindow maxWidth have been fixed.
I tested both fresh load and load from cache on IE7 and FF2 on a PC
described below. For fresh load I made sure I cleared the browser
cache before each load.
The results below are in msec recorded from testing done within 1
minutes in on
WinXP
1.80GHz Pentium 4
1G RAM
Fresh load (browser cache cleared)
================================
IE7
===
v2.x = v2.137c
6410 msec
5358 msec
5838 msec
v2 = v2.136d
4887 msec
4677 msec
4727 msec
v2.118 = v2.118
5288 msec
4387 msec
4526 msec
FF2
===
v2.x = v2.137c
2444 msec
2393 msec
2503 msec
v2 = v2.136d
2563 msec
2544 msec
1993 msec
v2.118 = v2.118
2624 msec
2343 msec
2303 msec
Load from browser cache
=======================
IE7
===
v2.x = v2.137c
3575 msec
3205 msec
3185 msec
v2 = v2.136d
2634 msec
2273 msec
2283 msec
v2.118 = v2.118
2494 msec
2484 msec
2653 msec
FF2
===
v2.x = v2.137c
2664 msec
2303 msec
2784 msec
v2 = v2.136d
2764 msec
2484 msec
2935 msec
v2.118 = v2.118
2303 msec
2574 msec
2403 msec
2.137c is slower than 2.136d and 2.118
Generally a lot slower and more significant differences in IE than in
FF.
Infowindow in 2.136d and 2.118 are not modularized.
~newton
On Nov 16, 10:55 pm, "pamela (Google Employee)" <pamela....@gmail.com>
wrote:
> Hey folks-
> We just pushed v2.137c as v2.x and v2.136d as v2. We don't have
> version aliasing implemented, so you'll need to specify the "c"/"d"
> if you're hard-coding to those versions for whatever reason.
> There were no bug fixes in 2.137c and no new features. There were some
> changes in modularization.
> The full changelog is available here:http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIChang...
> (If the groups interface cuts the link off, just find it in the wiki
> tab of the issue tracker).
> As always, please discuss anything in the forum that you think may be
> a regression and report in the issue tracker if others confirm your
> suspicions.
> - pamela
