GVH 2.4.1 performance
I'm moving a SL app to GE 4.3.1. It has 25 map services and about 160 map layers. I'm noticing some very sluggish performance if I turn on a few layers and start to pan and zoom frequently (as little as four or five pans in the course of three seconds). Pretty much everything slows down: layer draw time both on and off, map tip open time, etc. Even cached map services slow down as much as dynamic services.
I tested in Chrome and IE (surprisingly IE seems to perform a little bit better). Once the viewer starts to run slowly, it keeps running slowly. I also start get the Loading/Still Loading messages about map services, even though most of them aren't turned on in my viewer. It gets so slow that sometimes the layer list disappears (the data region just goes white), so it's not just the layers and map that are affected. The best fix is to refresh the page, but it will slow down again if I navigate the map too quickly.
Is a site this size unrealistically large to run well using the GVH on a desktop? I didn't see anything diagnostic in my ArcGIS Server or Windows logs, and I haven't seen any performance slow downs in my current version of the site, which uses the GE 4.1 and the GVS 2.2. It doesn't make sense that it should be an AGS issue since my other apps are fine.
And when the GVH viewer is running normally, it's blazing fast. I can click on a property that has 68 overlapping parcel polygons and get back all the map tips and flip through them faster than I can read them.
-
Hi John,
In GVH 2.4 we included functionality to support Web Content Accessibility Guidelines (WCAG) within our viewer. Due to this support, your viewer will make extra requests to allow for screen reading software to read out any changes to the map (Feature data that is visible, current extent, scale, etc.) whenever the map extent has been changed. I think this may be the reason why your viewer seems to slow down significantly when you change extent by panning/zooming.
You can turn off this functionality within the configuration json files on your server (Example: C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\<site_name>\Viewers\<viewer_name>\VirtualDirectory\Resources\Config\Default\Desktop.json.js) by performing a search for "MapTextProvider" and setting the "IsEnabled" property to false.
It should look similar to the JSON below.
"providers": [
{
"id": "MapTextProvider",
"type": "geocortex.essentialsHtmlViewer.mapping.modules.accessibility.MapTextProvider",
"decimalPrecision": 4,
"readAttributionInformation": false,
"isEnabled": false
}
]
Hopefully this solves the problem, if not I am glad to look further into the issue.
Cory Purnell
Latitude Geographics Quality Assurance Team0 -
Thanks for the fast reply and even faster fix! I changed that setting, and now the app is stabler and faster than ever.
That being said, we really appreciate the amount of work you've put into accessibility, and we want to provide that to our users. I'll either build a separate app or use the Tablet.json.js to configure a different, fully accessible viewer.
Please keep up the great work with WCAG; we're very proud to tell people about one of our vendors' work on the topic.
Best,
John Nerge
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
2 Kommentare