Legend and simple PNG performance issues

James Landwehr

04 Maj 2018 13:15

We are experiencing a couple of issues with regards to performance on a new Geocortex 4.9.2.46 site we are trying to launch that is running on an AWS instance. (It is a big site) When using Chrome's developer tools, I am seeing long fetch/draw times for a couple of items, namely legend features and some simple png's. (See below). I'm not sure where/how to disable this legend generation. It seems disabling the legend capability of layers doesn't turn the generation of them off. Also, these small png's and I'm not sure why they are taking upwards of 3+ seconds to retrieve and draw. 

 

GCE: Geocortex 4.9.2.46

 

GVH: 2.10

 

AWS: M5 2XL Instance with 8 VCPU, 32 GB RAM

 

 

The site is at: https://prd1.waukcogeo.com/HTML5Viewer/?viewer=html_viewer_ext

 

Thanks for any insights/tips.

 

 

_img_ alt="Legend issue" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=906f2000000botH&feoid=Body&refid=0EMf2000000ca1h" _/_img_

 

_img_ alt="PNG issue" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=906f2000000botH&feoid=Body&refid=0EMf2000000ca1m" _/_img_

0

• 

  Nico Burgerhart

  04 Maj 2018 13:57

  I've seen the same issue in a viewer.

   

  Could it be related to a maximum number of parallel requests to the server?

   

  I also notified legends for all layers were requested, even if they were not in the default layer theme.

  0
• 

  Zack Robison

  07 Maj 2018 18:28

  It's interesting that you're getting long waits for 304 responses, which means that you're just getting a message from the server telling your browser that you should have the image cached and why don't you look for it there instead of doing all this extra work.  This means that the server isn't drawing anything at all for those requests and my first guess would then be that it is simply overloaded with more traffic than it has resources for.  I would recommend considering a layer catalog in this case, if the only site with a problem is the one you're sharing.

  0
• 

  James Landwehr

  07 Maj 2018 18:37

  Thanks Zack. I considered a Layer Catalog solution, but all my testing with them have been disappointing. Sometimes the layers don't get added, sometimes added but no layer list change, sometimes a hanging layer list update. I suspect it has to do with the fact that the layers referenced in the catalog are part of multi-layer services so that is raising some issues. It's a great concept, but I'm not comfortable releasing something so new until it's working flawlessly. 

  0

Du måste logga in om du vill lämna en kommentar.