much slower performance with GE 4.9.1 and GVH 2.10.1
Recently upgraded from GE 4.6.1/GVH 2.7.1 to 4.9.1 & 2.10.1.
Our load times have jumped way up after the upgrade. Additionally, our Basemap no longer appears in Essentials Manager - so setting the initial extent is not possible.
It's a big, slow site in the best of times, which is our own design decision. However load times have basically doubled with the upgrade (from 15-20 seconds to 30+ now)
Looking at load times in the Dev tools, there are many items that take 6+ seconds to load - most are the 'legend?token=....' items, as well as the "..dojo.preventCache=..." URL, which at times takes over 12 seconds to load.
Site: https://maps2.tucsonaz.gov/HTML5Viewer/?Viewer=maptucson
Looking for some 'low hanging fruit' to pick in an effort to get our load times back to what we consider normal.
0
-
Al, that? not good news! Here I am trying to trim our 2.8.2 GVH load times, and then this comes along.
I have managed to trim a fair amont of time, and requests sent on initial load by trimming the excess fat from the desktop.json.js file. There are a bunch of modules in there that can be removed.
take a squizz at
https://docs.geocortex.com/essentials/gvh/2.10/admin-help/Default.htm#gvh/admin/modules.htm%3FTocPath%3DModules%7C_____0 for the list of modules.
Not ideal, as the upgrade if anything should spoeed things up. LG should by now know that it? a VERY heavy client
good luck0 -
4mb site JSON at 10 seconds to initialize is a big one. In terms of low hanging fruit I would setting up a layer catalog. Especially since it looks like the majority of the site is made of layers which are not even checked on at startup. This will kill performance running in any browser/device. A fantastic sample of a layer catalog implementation is iMapBC by the BC Government here. Check out https://maps.gov.bc.ca/ess/hm/imap4m/ (https://maps.gov.bc.ca/ess/hm/imap4m/) and let us know if you think that something that could benefit your Tucson app. 0 -
Oh and here is a video we made which will explain it all
https://support.geocortex.com/essentialsGSCVideo?sub-nav=videos&main-nav=essentials&#!/feedtype=SINGLE_ARTICLE_DETAIL&criteria=BESTANSWERS&id=kA560000000PBbZCAW0 -
Thanks Kevin -
We have a layer catalog version of this site, and may push it to be the only version available. It's not widely publicized yet.
https://maps2.tucsonaz.gov/HTML5Viewer/?Viewer=maptucsoncot
However I would still like to figure out what is going on with the new versions and our current site - I've since noticed a few additional issues, mostly with workflows not working (they load, and allow you to select an address, for example, from a drop down, but they end up timing out).
Again, understanding the current site is huge and clunky (our users are not ready to give up an all-in-one kind of site) - I'm discouraged that the new versions have added so much load time. Next step will be opening a support case, I think.0 -
Hey Allen,
The issue that you are having is the same as the one that I noticed and reported on November 3rd, 2017 with the release of GE 4.9. Each map action (pan/zoom) makes an unnecessary GET request to the MapServer Service URL that corresponds to (nearly) every layer in your map, regardless of whether or not those layers are turned off. These requests are all made with 'no layer selection' parameters (?layers=show:-1) which return blank PNGs every time, but the MapServer is still required to process the requests.
In your case, your Arizona map is requesting about 30 blank images on every mouse move which is adding a lot of work to your ArcGIS for Server.
*See screenshot for your Arizona site below:
We were fortunate enough to have caught this in DEV before we released the GE 4.9 update into our production environment. Geocortex support confirmed that the bug was slated to be fixed with the release of 4.11.0 -
Allen,
We upgraded over the weekend to v4.9.1 ( from 4.8.2) and the main issue we discovered ( besides slower maps) was a very slow identify operation, especially if you repeat the identify a few times. Yesterday, we applied the 4.9.2 update ( Essentials only) and map loading time as well as identify , are back to normal.
We were about to "undo" the upgrade when I noticed the update available as of 03/05/18. I hope this helps.
LR0 -
Thanks Liviu - that's reassuring to know. We'll apply the upgrade to 4.9.2 on our test environment and see it goes.
Allen0 -
I can confirm that after the 4.8.2 GE update, our viewer is still making many (15+) blank image requests to services that are turned off on every mouse-move.
The performance, howewer, has improved dramatically and the blank image requests are at least now 100% predictable. IE: Any Map Service loaded into the viewer that has at least one group-layer, or regular layer that is 'checked on' by default, but whos parent group-layer is turned off (so effectively the whole map service is inaccessible and grayed-out), will still be 'blank-requested' on each mouse-move.0 -
I'm surprised this still isn't fixed having raised a similar issue 2 years ago https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_DETAIL&id=906600000004IQzAAM If they're required it would be good to know why. If not why can't they be removed? 0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
9 kommentarer