Well i would like to thank you for your god points, and i have tried to implement most of them, but i still seemed to have issues with IE some improvements, but not the best performance.
But i have decided to drop the upgrade, to be honest i am not interested in putting that much work in a spare time project, to see minor map improvements from a users point of view anyway. Sorry that a could not show you the good result, but the new API and the performance work this has to stop for me. Cheers. On Apr 6, 8:44 am, Ben Appleton <[email protected]> wrote: > Try running Google Page Speed on your site. The main issues that it calls > out: > > - All of your images and CSS are missing HTTP cache headers. Specifying > HTTP cache headers helps to reduce latency. > - If you obfuscate and gzip compress your JS and CSS they should reduce > in size by 5x or so. > > Also you should sprite the flags on the right side of your map, and consider > spriting your MarkerImages. Spriting reduces the number of HTTP requests > that the browser has to make. > > A couple of v3-specific optimizations to try: > > - I see that you first create an InfoWindow, later create a Map, and even > later create some Markers. The delay between each causes the JS modules > for > InfoWindow, Map, and Marker to load separately. If instead you create your > InfoWindow when you create your Map, and create a dummy Marker at the same > time, the API will "sprite" these JS modules into a single download. > - Try creating only one instance of MarkerImage for each icon, and > reusing instances between Markers. That saves a some work inside the API > which should speed up Marker rendering. > > Let us know if these optimizations help or not. > > Cheers > Ben > > > > > > On Mon, Apr 5, 2010 at 9:32 AM, rcheli.dk <[email protected]> wrote: > > Thanks Marcelo > > > I have change the overwriting and the loop :) > > > But not a big change in IE !!! any other good proposal ? > > > On Mar 31, 11:48 am, Marcelo <[email protected]> wrote: > >> On Mar 31, 10:24 am, "rcheli.dk" <[email protected]> wrote: > > >> > Any input would be great. > > >> hhhmmmm ... You're overriding the API's own methods, so I am not sure > >> I want to get my hands in there. > > >> In any case, this looks like an endless loop: > > >> google.maps.Marker.prototype._setMap = > >> google.maps.Marker.prototype.setMap; > > >> google.maps.Marker.prototype.setMap = function(map) { > >> if (map) { > >> map.markers[map.markers.length] = this; > >> } > >> this._setMap(map); > > >> }; > > >> -- > >> Marcelo -http://maps.forum.nu > >> -- > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Maps JavaScript API v3" group.> To post to this group, send email to > > [email protected].> To unsubscribe from this group, send > email to > > [email protected]<google-maps-js-api-v3%2B > [email protected]> > .> For more options, visit this group at > > http://groups.google.com/group/google-maps-js-api-v3?hl=en. > > > > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
