I put 3 tile layers on a map each as their own OverlayView. I also put the same 3 tile layers on a map in the same OverlayView. On an iPhone, there is a pretty significant performance difference between a single layer and 3 layers. However there was not a noticeable difference between 3 layers in a single OverlayView or in multiple OverlayViews. This may be due to the fact that I throttle the bounds_changed event to only fire once a second. This leads me to believe that the vast majority of the performance degradation with multiple layers comes from the rendering and memory usage of that many DOMNodes and images rather than from the events. Of course at much higher numbers of layers there may indeed be a significant difference, however this seems to be a pretty specialized optimization.
If I needed to display large numbers of tile layers simultaneously, I personally would pursue a server side solution rather than having the client render that many layers. Of course not everyone may have that option. Using my class, the performance of the map with 3 layers is acceptable. Beyond that, your mileage may vary. Chad Killingsworth On Nov 29, 8:26 pm, Peter Dang <phucdaid...@gmail.com> wrote: > Yes, I agree with Bratliff about your option, so we need to manage a > multiple tile sets in > a single OverlayView. > > Cheer, Thanks a lot Chad for your support in file js. -- 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.
