sfairgrieve
commented
10 years ago Thanks for pointing this out. I should probably do more testing in IE ;). You're right, the drop shadow effect definitely slows down performance, so I imagine setting dropShadow to false would speed things up considerably. I'll also look into other ways of optimizing drawing speed/performance.
On Friday, February 7, 2014, Matthew Sabol notifications@github.com wrote:
I've had some issues when loading many markers (specifically 1,312) on a map. It could take up to a minute depending on the number of markers. Chrome, Firefox, Safari, and Opera do not have this issue. I have a feeling it's SVG rendering.
The work around for this was to force load IE9 for all versions of IE. I don't particularly like this option, but the load times are back to 0.1 - 2 seconds.
I did look at other plugins for leaflet and they didn't seem to have this same problem. I have yet to disable shadow or other svg elements to see if this improves load time (I suspect it would).
I don't plan on removing the IE9 tag until I do some more tests, but I figured I would write up an issue to document this (even though it's probably a low priority - especially since IE in general renders the DOM very poorly... and I don't expect you to rewrite IE for them, though you'd probably do a pretty decent job).
Reply to this email directly or view it on GitHubhttps://github.com/humangeo/leaflet-dvf/issues/18 .
I've had some issues when loading many markers (specifically 1,312) on a map. It could take up to a minute depending on the number of markers. Chrome, Firefox, Safari, and Opera do not have this issue. I have a feeling it's SVG rendering.
The work around for this was to force load IE9 for all versions of IE. I don't particularly like this option, but the load times are back to 0.1 - 2 seconds.
I did look at other plugins for leaflet and they didn't seem to have this same problem. I have yet to disable shadow or other svg elements to see if this improves load time (I suspect it would).
I don't plan on removing the IE9 tag until I do some more tests, but I figured I would write up an issue to document this (even though it's probably a low priority - especially since IE in general renders the DOM very poorly... and I don't expect you to rewrite IE for them, though you'd probably do a pretty excellent job).