[Geomoose-users] Performance issues

[Jeffrey Schmitz]

Thanks for the responses!

We were using WMS for two reasons: we wanted to make our data easily
accessible, and we wanted to take advantage of tiling so that users
could move the map around without the need for it to refresh
continually. This week, we tried disabling the tiling, and performance
improved significantly, to be just about as quick as using them as map
server layers. Any idea why tiling would create such a drastic
decrease in performance?

Also, our mapbook is rather large (we have quite a few layers), so I
included a snippet of what a typical map source entry looks like when
we use WMS with tiling:

<map-source name="hashed_layers" type="wms" tiled="true"
queryable="false" projection="EPSG:900913">
               <url>http://maps.glifwc.org/development/glifwc_wms.php</url>
                       <layer name="mn_bathymetric_contours"/>
                       <layer name="cooperative_weed_management_areas"/>
                       <layer name="eab_quarantine_counties"/>
                       <layer name="minor_watersheds"/>
                       <layer name="major_watersheds"/>
                       <layer name="great_lakes_watersheds"/>
               <param name="format" value="image/png" />
               <param name="TRANSPARENT" value="TRUE" />
       </map-source>

Thanks again for the help!
-Jeff

On Tue, Jul 27, 2010 at 9:29 AM, Brent Fraser <bfraser at geoanalytic.com> wrote:
>  Are you using the same map file for both WMS and Mapserver CGI?
>
>  While I've used mapserver as a WMS server to produce a single image per
> request, I've never used it to produce WMS tiles.  Can you give more details
> on your config?  What does your mapbook map-source entry look like?  What
> does the WMS CGI request(s) look like?
>
> Best Regards,
> Brent Fraser
>
> Jeffrey Schmitz wrote:
>>
>> Hey guys, I am having performance issues, and was wondering if anyone
>> had any tips on how we could possibly speed up our site. Our current
>> setup:
>>
>> We have a postGIS table with data in WGS84(EPSG:4326). It is defined
>> such in our mapfile layer definitions, and projected by mapserver as
>> Web Mercator (EPSG:900913) for web map services, which are served by
>> geomoose.
>> Currently, with only a couple of layers turned on (Wisconsin,
>> Minnesota and Michigan counties, and the great lakes), our site takes
>> a LONG time to load (45seconds to a minute). It appears to me that
>> this is an issue with our setup, not network speed. If launched in
>> firefox, you can see that the page loads fine, but is slow when
>> loading the wms tiles (you see "waiting" for a while and then
>> "transferring"  for a couple seconds, and then "waiting" again for
>> long periods).
>>
>> We also have an identical site that uses mapserver and mapfiles
>> directly instead of WMS, and it loads in everything in just a couple
>> of seconds.
>>
>> Does anyone have any suggestions as to why we would be seeing such
>> significant slow down when using web map services?
>>
>> Thanks for any help!
>>
>> Jeff
>>
>>
>> ------------------------------------------------------------------------------
>> The Palm PDK Hot Apps Program offers developers who use the
>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share of
>> $1 Million in cash or HP Products. Visit us here for more details:
>> http://ad.doubleclick.net/clk;226879339;13503038;l?
>> http://clk.atdmt.com/CRS/go/247765532/direct/01/
>> _______________________________________________
>> Geomoose-users mailing list
>> Geomoose-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geomoose-users
>>
>
>