I don't think it's markerclusterer. It's the API itself that has got *much* slower in recent builds (after 3.13), particularly in Chrome browser. It exhibits the same problem with large numbers of points, even if markerclusterer isn’t used. As far as I can tell it seems to be the google.maps.Marker() constructor that is so much slower than it used to be in Chrome.
I've reported it as a bug here 6140<https://code.google.com/p/gmaps-api-issues/issues/detail?id=6140> but Google has so far not acknowledged it as a problem. For me it's a huge problem and using large numbers of points has become unusably slow in Chrome. It's fine in Safari though! (Which I'm sure isn't what Google would really like). I've posted simple code that demonstrates the problem in my bug report. If others who have the same problem could 'star' my bug report, there might be more of a chance that Google will notice and do something about it. Mike On Friday, January 24, 2014 3:20:14 PM UTC-6, uno wrote: > > hello, > i've just updated markerclusterer plus from 2.0.15 to 2.1.1 and sit seems > way slower in processing the clusters (20k markers). > before i dig into it, i wanted to ask if someone has made a similar > observation? > thanks, uno > > -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-maps-js-api-v3+unsubscr...@googlegroups.com. To post to this group, send email to google-maps-js-api-v3@googlegroups.com. Visit this group at http://groups.google.com/group/google-maps-js-api-v3. For more options, visit https://groups.google.com/groups/opt_out.
