Hi Johan!<br><br><div class="gmail_quote">2011/4/11 Johan Sandberg <span dir="ltr"><<a href="mailto:johs@kth.se">johs@kth.se</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hey!<br>
<br>
I am performing tests with the software LoadUI. I have pregenerated URLS from a listw which the programe reads.<br>
The backend WMS are a geoserver which is pretty fast. MapProxy is installed on a linux computer running on apache2 with the WGSImode.<br>
<br>
For the fourth test (1600*1200) the WMS the avarage time is better for WMS than for MapProxy.<br>
The tests are fetching the same data which are severall vector layers compose as one Map layer.<br></blockquote><div><br>If you are planning to serve large images via WMS it is probably a good idea to increase your tile size [0].<br>
<br>Mapproxy defaults to tiles with 256x256 pixels. If you request a 1600*1200 pixel image MapProxy has to fetch and glue together 7*5=35 tiles, which adds up latency and negates the advantage of having a proxy.<br><br>If you increase your tile size to 512x512 pixel MapProxy only has to fetch 4*3=12 tiles which should help in reducing your latency.<br>
<br><br>cu andreas <br><br><br>[0] <a href="http://mapproxy.org/docs/1.0.0/configuration.html#tile-size">http://mapproxy.org/docs/1.0.0/configuration.html#tile-size</a><br></div></div>