Wasn't it Brett who wrote: > >I'm still a little confused at how encoding polylines would make a big >difference in the discrepancy between load times for IE and Firefox. I >will go ahead and learn and get in the practice of encoding my >polylines, but I still don't think this is the reason underlying IE >being so much slower than firefox in this case.
It probably won't, but it will speed up the (uncached) load times across the board. When comparing load times, be careful to compare situations in which the caching situation is the same. If you've been testing with Firefox previously, it will have your XML file in cache. If MSIE doesn't have that file in cache, then your timing would include the time to fetch that 1735kb file. Fetching 1735kb of data would be expected to take a minimum of 11 seconds over a 1.5Mb/s Internet connection. When I tested it, it took 14.049 seconds to fetch your XML file, out of a total of 23.243 seconds to render the page in MSIE7. If you could halve the size of that file, you'd save 7 seconds. Other things that would speed up the loading of that page would be: * Shrink things like dc_side.jpg. Consider using an image that has a height of 1 pixel and either stretch it or use it as a background rather than as an <img>. Because every horizontal line in that image is identical, the extra 965 lines don't need to be fetched. * Lower the quality settings on your JPG images, or consider using a different image format (e.g. GIF). I suspect that there may possibly be something wrong with the image processing software that created your JPGs. With Paint Shop Pro, setting all the JPG quality parameter to the absolute maximum, the file size is less than half what you've got. Lowering the JPG settings should produce images that are visually indistinguishable from what you currently display, but with about a tenth of the file size. * Move things like dc_side.jpg, dc_banner.jpg, rosendahl.jpg to a different subdomain. [MSIE will only open two channels to each subdomain, and one of the www.terevaka.net channels is completely tied up loading the XML file, so you don't get any parallelism in the image loading. You can't move the XML file because of cross-domain security considerations.] However, the bottom line is that 690 polylines will always be slow to load. Consider either reducing the number of polylines or using images (GGroundOverlay or GTileLayerOverlay) instead of polylines. -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
