I have had the same issues as well. The problem isnt so much the Google Map API, but the underlying dom elements that must be inserted when a marker is created. For our map, marker manager was not a good solution, so we had to implement a custom map manager. I suggest using an instance of MarkerLite and using some sort of batching algorithm to add and remove markers from the map. The script taking to long is caused by the browser seeing a loop that is taking too long, and this is usually because your are calling addOverlay within the loop. Instead of looping of a large set of markers, I batch them, say in groups of 200, using a background process called with setTimeout. I implemented a solution like this and got rid of the unresponsive script dialog.
On Dec 3, 3:16 pm, "Postholer.Com" <[email protected]> wrote: > From my experience, 300 markers works reasonably well. A 1,000+ *will* > impact user experience with the dreaded "script taking to long" > message. > > I would strongly suggest using the open source marker manager from the > start. Your site will grow into it as markers are added: > > http://code.google.com/p/gmaps-utility-library-dev/ > > -postholer > > On Dec 3, 8:40 am, gozimmer <[email protected]> wrote:> Regarding speed > on map markings... > > How does heavy map marking affect google indexing > > How Many Map Markers are recommended... ie 5 to 25, 25-50, 50-100, > > 100+, > > Site Link -http://gozimmercoil.touristwayapp.com/index.cgi -- 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.
