Comments for Optimizing OpenLayers at http://www.geowebguru.com , comment 1 to 3 out of 3 comments http://www.geowebguru.com Fri, 30 Jul 2010 12:25:40 +0100 FeedCreator 1.7.3 http://www.geowebguru.com/articles/212-optimizing-openlayers#comment-136 Thanks for the suggestions. If anyone has any recommendations for speeding OpenLayers, then feel free to add them to this thread. "Anonymous": Good idea. Also the build script does "compress" the Javascript by removing all pretty printing. HTTP compression would cut this further, and also speed many of the data downloads (eg. KML). Paul: Yes in theory this is a much better approach. However, when starting from scratch it is difficult to know exactly which components are required. Some are obvious (eg. I needed the GML layer support for KML) but others are not, so a trial&error approach is still required. The [first] section would also have to be cut back, and it would be a case of adding lots of things until it works. It is easier to start with something that works, rather than to try to keep adding things until it does. Perhaps the output from my build script could be used as a basis of a script along the lines that you describe. The end result would then be the more stable build (as you describe). - Richard Marsden Tue, 06 Oct 2009 03:27:44 +0100 http://www.geowebguru.com/articles/212-optimizing-openlayers#comment-135 If you are going for a minimalist build, try using include to keep the things you know you want rather than exclude the things you don't. The advantages are that the list will (probably) be shorter, you know you have what you just what you need plus dependencies, and you don't need to change when updating to a newer version that has new things to be excluded. - Paul Spencer Mon, 05 Oct 2009 09:52:45 +0100 http://www.geowebguru.com/articles/212-optimizing-openlayers#comment-134 How about enabling HTTP compression? That should reduce the needed bandwidth by about 90%. - - Mon, 05 Oct 2009 08:53:44 +0100