[Geomoose-users] GeoMoose 3 - Speed

Sun Feb 2 10:47:33 PST 2020

Chris,

Are you using the same MS4W version for both applications?  If not see what MapServer version each is using and check to make sure you have indexes built for both on the data source.

Brian

        Brian Fischer
{Title}
Houston Engineering, Inc.
O 763.493.4522 | D 763.493.6664 | C 763.229.2734
        [cid:hei_d562a228-8e53-424d-8c69-43b1a222b74e.png]      7550 Meridian Circle North, Suite 120
Maple Grove, MN • 55369
www.houstoneng.com<http://www.houstoneng.com/>
Follow us: Facebook<https://www.facebook.com/houstoneng> | Twitter<https://twitter.com/houstoneng> | LinkedIn<https://www.linkedin.com/company/houston-engineering-inc.> | YouTube<https://www.youtube.com/user/HoustonEngInc>

This entire message (including all forwards and replies) and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret, work-product, attorney-client or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

From: Geomoose-users <geomoose-users-bounces at lists.osgeo.org> On Behalf Of Dan Little
Sent: Sunday, February 2, 2020 12:12 PM
To: TC Haddad <tchaddad at gmail.com>
Cc: geomoose-users at mail.osgeo.org
Subject: Re: [Geomoose-users] GeoMoose 3 - Speed

[External Email]
________________________________
I was going to suggest tracking down the issues with the mapfile. We actually did some initial benchmarking in GM2 vs GM3 development and there are a lot of code paths that actually ended up faster. But I do admit sometimes the data transfer + parsing can make a service call feel less responsive.

On Fri, Jan 31, 2020 at 7:47 PM TC Haddad <tchaddad at gmail.com<mailto:tchaddad at gmail.com>> wrote:

Is there a reprojection happening in your 3.x setup that wasn't happening in your 2.x setup?

On Sat, Feb 1, 2020 at 1:56 AM Christopher Hughes <chughes at co.lincoln.or.us<mailto:chughes at co.lincoln.or.us>> wrote:
I'm using WMS for display and WFS for queries. The surveys dataset I mentioned is connecting to a postgis server,
whereas the rest of my data are in shapefiles on the same server. Looking at shp2img it looks like it's in the drawing
of the layer rather than in the web service.

Shp2img results:
-msDrawMap(): Layer 0 (Surveys), 0.043s             -    using mapfile from geomoose 2
-msDrawMap(): Layer 0 (Surveys), 7.219s             -    using mapfile from geomoose 3

Although that kind of points to my mapfile configuration. I'll continue debugging.

Chris

On Fri, Jan 31, 2020 at 3:36 PM James Klassen <klassen.js at gmail.com<mailto:klassen.js at gmail.com>> wrote:
How are you loading the data in GeoMoose 3?  In GeoMoose 2 I'm guessing it was via WMS.

Where are you seeing the bottleneck?  The web service or inside GeoMoose proper?

Generally speaking...

If you are using WMS then load times should be similar.

If you are using WFS it might be faster or slower on initial load depending on the amount of vector data transfered.  I think GeoMoose will pass a bounding box to the WFS server so if you zoom in first it might help.  It should be faster than GeoMoose 2 on interactions after initial data load.

GeoMoose 3 also supports using a WMS layer for display but a WFS later for query.  That might help the initial load times.

On Fri, Jan 31, 2020, 15:27 Christopher Hughes <chughes at co.lincoln.or.us<mailto:chughes at co.lincoln.or.us>> wrote:
Does anyone have any advice on how to improve data rendering speeds for GeoMoose 3?

I'm having some issues loading vector data quickly, although our imagery does also load a
bit slower than in our GeoMoose 2 website. I'm on Windows but it doesn't appear to be
inherently a Windows vs Linux issue. I can load our surveys dataset with GeoMoose 2
in around 2 seconds, but when I switch to GeoMoose 3, the same dataset on the same server
takes around 10 seconds to load.

I've noticed that the services run very quickly. I can search or select data about as quickly
as on GeoMoose 2, but when it comes to then zooming to results and rendering the data
there's a significant lag, even when comparing GeoMoose 2 and 3 when on the same Windows
server.

Thanks for any suggestions,

Chris

--
Chris Hughes

GIS Analyst
Lincoln County Surveyor Department
880 NE 7th St. l Newport, OR 97365
Tel: (541) 574 1283
_______________________________________________
Geomoose-users mailing list
Geomoose-users at lists.osgeo.org<mailto:Geomoose-users at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/geomoose-users<https://lists.osgeo.org/mailman/listinfo/geomoose-users>

--
Chris Hughes

GIS Analyst
Lincoln County Surveyor Department
880 NE 7th St. l Newport, OR 97365
Tel: (541) 574 1283
_______________________________________________
Geomoose-users mailing list
Geomoose-users at lists.osgeo.org<mailto:Geomoose-users at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/geomoose-users<https://lists.osgeo.org/mailman/listinfo/geomoose-users>
_______________________________________________
Geomoose-users mailing list
Geomoose-users at lists.osgeo.org<mailto:Geomoose-users at lists.osgeo.org>
https://lists.osgeo.org/mailman/listinfo/geomoose-users<https://lists.osgeo.org/mailman/listinfo/geomoose-users>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20200202/bcfa6948/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hei_d562a228-8e53-424d-8c69-43b1a222b74e.png
Type: image/png
Size: 986 bytes
Desc: hei_d562a228-8e53-424d-8c69-43b1a222b74e.png
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20200202/bcfa6948/attachment-0001.png>