On Apr 1, 3:37 pm, Chris Apolzon <[email protected]> wrote:
> I think the main culprit (slow IE) is IE's use of VML instead of SVG or
> Canvas for graphics support. IE7's javascript engine is also fairly slow,
> but IE8's is really not that bad.
> I do agree though, if you want a snappy-feeling map experience you cannot
> use IE. If you're supporting IE users, a recommendation of Chrome Frame
> never hurts.
Hi Chris,
I have made some recent performance improvements to PolyCluster. If
you have not updated your copy within the past couple of weeks, you
ought to do it.
In the case of VML, a tile size of 1024 x 1024 works quite well. In
the case of both SVG & CANVAS, a tile size of 1024 x 1024 seems
unreliable. The tile sizes are set accordingly for the different
browsers. I do not know what tile sizes are used by the API but I
suspect it is 256 x 256 regardless of browser.
For really large polys, the tile size of 1024 x 1024 makes Internet
Explorer competitive with other browsers. It also avoids "Script
running slowly" messages. I am in the midst of another optimization
for ridiculously large polys (US Highways with 1.5 million vertices).
I expect to be done next week.
You can experiment with adjustable tile sizes with the "Experimental"
demos.
http://www.polyarc.us
If you discover other tile sizes are suitable for other browsers,
please let me know.
Thanks very much.
Berry
--
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.
