I have an application that was upgraded to the 100.4 version of the API. In testing this application I see huge difference in the overall performance of the identify. What is odd is that not all layers perform worse, some actually seem to perform better. However, the ones that perform worse are significant (4 seconds in one case, 1.5 in another). While I have not done an exhaustive evaluation of the layers themselves, it would seem that layers with more data a decrease in performance of the largest amounts.
What is going on here? Because of the magnitude of the increase with specific layers I have an identify operation go from 0.6 seconds to 7.5 seconds. It should go without saying that having a user wait 7 seconds for identify results is not acceptable
I also observe a noticeable difference in the performance of a polygon search on a large offline database although I have not logged the actual performance.
These tests are using the same offline replicas, identifying the same layers. The only difference being, I changed the API from 100.4 to 100.2 (and fixed the breaking changes)
|Layer Name||Time Seconds (API = 100.4)||Time Seconds (API = 100.2)||Increase (ms)||Identify Time Change|
|Repaired Gas Leaks||0.256843||0.0079967||24.88463||Increase|
|Non Critical Valves||0.1778903||0.0189875||15.89028||Increase|
|Pressure Monitoring Device||0.0199876||0.0179843||0.20033||Increase|
|Sniff Test Location||0.0259856||0.0189887||0.69969||Increase|
|Gas Pipe Casing||0.0169889||0.0169911||-0.00022||Decrease|
|Customer Service Zones||0.0169903||0.0189886||-0.19983||Decrease|