Organizations, government, and business rely on their web apps, web maps and web services for their daily workflow. Making sure your web app is consistently up and performing well is critical to your business and important to your customers and perhaps for the public. GEO Jobe works with a number of agencies that rely on us to provide these services.
If your Web Application is not performing to your or customers liking there are a couple of things you can check and try.
- The first and probably the most obvious is check your network and hardware.
- Next, check the database. Run a compress, rebuild indexes, and analyze.
- Look into recreating your spatial indexes
- Then check the feature classes for data quality issues, such as those having zero shape lengths, or areas.
A good way to check if your underlying database is the issue to see how it performs in ArcMap. If it draws slow there it will definitely cause your application to have performance issues.
However, if you checked through the stack and everything checks out then it’s time to look at what is rendered when your web application initially loads.
For instance, we host databases and map/feature services for several county assessor offices that support our Property Search Application (PSA). Our best performing PSA’s keep the amount of default rendered features to a minimum, they keep the symbology simple, utilize drawing scales and they take advantage of Esri’s tiled basemaps. These PSA’s perform great and a good example of this is the Shelby County, TN PSA When these PSA’s load the only layer layers that render initially are the political boundaries and the Esri Streets basemap. If the user needs additional layers to draw, such as the property annotation, then the user can turn those layers on as needed. What this scenario of keeping default layers to a minimum does is:
- Lessens the load on your servers
- Keeps the application clean
- Improves user experience
Slower rendering PSA
Fast rendering PSA
It sounds like common sense, but in the process of creating these applications the urge to have all these layers come on when the app loads is strong. But I urge you to step back and really think through what really needs to be shown when the app loads for your end user.
GEO Jobe has experience working with customers from a range of disciplines and we help them to build, deploy, and manage their web services and ArcGIS Enterprise infrastructure. We’ve learned many hard lessons maintaining our GEOPowered Cloud shared hosting environment and if we can help in any way please contact us.
Looking for more ArcGIS related technology Tips? See here