Depending on the speed of you map when your using my OpenLayers based MapGuide tiling tool, the browser might actually be the bottle neck.
I did a little experiment today, it involves using google chrome and adding
some css to the page to stop the browser rendering the tiles.
Simply add the following style definition to the tiler script
<style type="text/css"> img {display:none;} </style>This speeds up things quite a lot, especially when you already have some of the cache already seeded.
It also helps to use multiple urls to avoid the browser limitations of http connections per host name.
1 comment:
It turns out chrome ain't really as mature as firefox when it comes to heavy long running javascript...
chrome crashes after a running the tiler for a while
Post a Comment