On May 23, 3:05 am, Dave <dualrud...@gmail.com> wrote: > The biggest time user is the following call chain: > Function.apply -> e -> eval code. >
I've tried to replicate these results using the IE8 profiler. First I saved a copy of the marker data and made a simple page with default markers: http://www.william-map.com/20100525/1/markers.htm Then I measured page load in Quirks and Standards mode. You can see the markers slowly rendering in Standards mode. Page Load Results. Time: Browser Mode 3.84s IE8 Standards Mode 1.75s Quirks Mode Standards mode is 2.09s slower Major difference is a section of "Eval Code" (I guess any code in a module is called Eval Code). Time: Browser Mode 2.25s IE8 Standards Mode (58 percent of total run time) 0.09s Quirks Mode Standards mode is 2.16s slower for this section of code. The code includes calls to the following functions 312 calls to Xd() 322 calls to R() 644 calls to hi() from what I can see, R() and hi() create a google.maps.Size() object, so this isn't likely to be a problem. Xd() sets the width and height of a DOM object. This is more likely to be the problem, given the difference between Standards and Quirks mode is due to the box model. Perhaps in Standards Mode, setting the height and width of a block element in a Marker causes the browser to recalculate the sizes and positions of the entire map DOM elements? also see an older issue which looks a bit similar: http://code.google.com/p/gmaps-api-issues/issues/detail?id=1829 -- 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 google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
