Since v2.118, I applied elapsed time from GMap API js request to infowindowopen on the 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 changed the version # in the API loader url and load the page 3 times for each version. I made sure I cleared the browser cache before each load. The results below are in msec recorded from testing done within 2 minutes in IE7 on WinXP 1.80GHz Pentium 4 1G RAM 2.130d ------ 5067 5258 5338 2.129e ------ 5437 5488 5428 2.118 ------ 4436 4367 4316 Slight improvement in 2.130d over 2.129e but still slower than 2.118 On Sep 28, 11:54 pm, "pamela (Google Employee)" <[EMAIL PROTECTED]> wrote: > Hey developers- > > Last night we pushed v2.130d as v2.x and 2.129e as v2. We don't have > version aliasing implemented, so you'll need to specify the "e" if > you're hard-coding to those version for whatever reason. > > There are currently no changes in 2.130d. > > 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. > > The full changelog is > here:http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIChang... > > - pamela --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to Google-Maps-API@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
