Hi, I'm in the processing of needing to optimize a maps application for Americorps VISTA - http://www.thevistamap.org/. Basically, right now we're using v2 of the API and marker clusterer (as well as a custom additional clustering layer I wrote to handle pins that are right on top of each other for people who don't enter a streed address, e.g. all pins for Salt Lake City, UT get clustered before the marker clusterer does its work) to produce a timeline-based map of all the different VISTA members and there services.
With a few hundred users, this solution has worked fine, but we're about to send out a mass email asking all VISTA alumni to add there services, so I ran some scalability tests with 1,000, 10,000 and 20,000 users. This gets painful really quick, especially since for each user, there's a marker for each year after their service, i.e. the exponential curve gets steep quick. I know a few things I can do to speed things up, but I wanted to get the group's opinion on what will have the most success. Will upgrading to v3 have much, if any impact on keeping track of potentially 100k markers (being shown at different times depending on what year is being shown)? Do I need to go to a server-side clustering solution? I started looking at the KML and Fusion Tables solutions mentioned on the Geo Developers blog recently, but don't know if either of these will be the right solution for me. Thanks for any advice or insight. Cheers, Trey -- 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.
