<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello,<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>We've been using Mapserver as, among other things, a WMS server for some time with satellite and aerial imagery, without problems. We've been able to serve imagery of resolutions down to .25 meters without any significant performance hit.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Today, we got a sample image from a new source, which has a resolution of 0.06 meters. The image is 317 megabytes in size, and has dimensions of 17538 x 19035 pixels. The file size is smaller than many of the Landsat or other images that we have displayed in the past. However, we're finding that rendering this image is extremely expensive. In particular, with tiled access, a la Google Maps, the WMS requests bog down our server to the point where all of its memory is consumed.</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>I know that overviews, tiling, and such, are good strategies for reducing the render time on a large area, reasonably high resolution image. But what would be good strategies for improving rendering time on this smaller, ultra-high resolution image?</div><div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">--<br>Avi Blackmore<br>Head Programmer/System Administrator<br>Satshot Inc.</span>
</div>
<br></div></body></html>