This is the overview page for a set of test cases that examine how many tracks can be displayed simultaneously by the Google Maps API.
Each case presents a number of tracks to the Google Maps API. The idea is to see how many tracks the API can cope with before it becomes unreasonably sluggish. This point will depend on the browser, operating system, etc - even so, it is hoped that these cases provide some insight into the API's practical limits.
Note that some tracks consist of multiple segments, thereby increasing the browser's workload. Most of the tracks are in the Wellington region, though Case 5 and Case 6 include tracks scattered around the country.
It is probably best to view one case at a time. Things to do include zooming, scrolling, and changing map type (including to/from "Earth 3D"), to see how well the map performs.
The track data is encoded, which improves the efficiency of the API's rendering relative to using a kml file directly and hence allows more tracks to be displayed.
Test cases: