Unless your data is changing very frequently, generating a static file with a cron job would probably be the way to go. I'm guessing that alone will massively improve your response times.
Chad Killingsworth On Sep 30, 2:25 am, Niklasro <[email protected]> wrote: > On Sep 29, 1:25 pm, Chad Killingsworth > > > > > > <[email protected]> wrote: > > It takes me over 5 seconds to loadhttp://www.montao.com.br/output.kml. > > My guess is that the request is timing out on the client but on the > > second load you are getting a cached version from Google's servers. > > > Fix the loading time of your kml file. > > > Chad Killingsworth > > > On Sep 29, 4:12 am, Niklasro <[email protected]> wrote: > > > > Hi > > > Map in question ishttp://www.montao.com.br/ > > > Where all is well 2nd hit when KML markers load. It seems from here > > > markers load on reload only. Do you get the same strangeness or is it > > > my client? Can you recommend how I should update? > > > Thanks > > > Niklas > > Thanks! It appears generating the KML causes it. I can try fetch fewer > markers. The KML also can be made pre-generated and refreshed instead > of like now dirty generating the output directly making too many calls > to the data layer. It doesn't need to be that dynamic and can get made > a cron job reloading every hour and storing itself like a blob or > likwise. Do you agree? > Thanks > Niklas -- 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 [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-js-api-v3?hl=en.
