igloo wrote: > On OS X 10.5.6 (2.4 GHz Intel Core 2 Duo): > > Safari 3.2.1 - 230 - 1 > > Firefox 3.0.4 - 440 - 1.9x slower > > Camino 2.0a1 - 480 - 2.1x slower (This comes from the same stable as > Firefox so one would expect the results to be close) > > However, in loading slightly complex Google Maps, the difference > between Safari and Firefox is not noticeable. > > That's the problem with benchmarks. At least this one tries to be > general, but no two Javascript applications are going to use the same > mix of object classes... > > Interesting comparisons, but should be taken with a grain of salt. > Correct and javascript isnt all a given page does. But, It gives a base line worth considering I have some pages loading too large of kml with my GeoXml class, that I have used similarly for timing ...
Point is Yes virginia ... IE (especially 6) is exactly as bad as we think it is. orders of magnitude slower with many different tests not just google maps. And 7 is still very slow even if better than 6. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
