Indexing tables is one way to improve performance, especially the following tables and fields:
ACONNECTIONOBJECTGLOBALID + ACLASSMODELNAME
This is the most frequently queried table in Fiber Manager, and it typically has the greatest number of rows.
Queries almost always reference the GlobalID and model name fields together (for example:
SELECT * WHERE CONTAINERGLOBALID = x AND CONTAINERCLASSMODELNAME LIKE y).
BCONNECTIONOBJECTGLOBALID + BCLASSMODELNAME
CONTAINERGLOBALID + CONTAINERCLASSMODELNAME
FIBERCIRCUITGLOBALID (see note)
For all tables, remove the index on the FIBERCIRCUITGLOBALID field; it is no longer referenced by Fiber Manager.
- For performance of ArcGIS Server, monitor the number of active instances created for the GIS service that Wavepoint uses for the Fiber Manager data. If the maximum number of instances are usually in use (check the ArcGIS Server Manager interface to see this), try increasing the maximum number of instances and test to see if this helps Wavepoint performance for the end users.
Other settings can influence the ArcGIS Server performance as well, such as:
Forcing text anti-aliasing
The fonts selected for the layers in the published map service
Logging levels enabled
Re-projecting data from more than one coordinate system
When compared with the ArcGIS Server or the database server, the IIS service (which runs the Wavepoint application) has the greatest need for hardware resources (CPU cycles and memory). Ensure that adequate memory is available on the server hosting the IIS service. An experienced IIS administrator might also be able to help tune the cache and other settings for best performance.
If requests for basemap tiles are causing problems for Wavepoint users, you might try hosting a tile cache locally, or test using a custom basemap hosted on your ArcGIS Server to increase performance.