Sorry for not making a clear point... I wasn't talking about loading speed of the entire map, but performance on the client while working with about 5k markers, 20k polylines, 10k polygons... If they all are overlayed as vector graphics (canvas, svg), on every browser there's a major performance drop. Markers are easy, they can be managed with MarkerManager, MarkerClusterer or something else, but the polylines and polygons seems to be verry heavy. If all of them are overlayed as tiles, it will be much faster. I think this is exactly the purpose of KmlLayer, correct me if i'm wrong v2 documentation says that getTileLayerOverlay() method of GGeoXml is deprecated.
On May 29, 1:02 pm, Pil <[email protected]> wrote: > On May 29, 9:54 am, Yordan Yordanov <[email protected]> wrote: > > > so it will not boost performance like KmlLayer > > I believe it's a story that v3 is faster than v2. > v3 has very heavy background loading. The DOM will be built completely > after the map seems to be ready to use. Actually there is no > performance boosting, but the loading technique has been changed. > Thats the new catch. > > BTW: Just tried it out: v2.140 (incl. GGeoXml) loads even faster than > the current v3 (incl. KmlLayer). -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
