OK so I've been running various Identify Performance Benchmark against Geodatabase for v100.2, 100.2.1, 100.3, 100.4 and latest 100.5 build, and I'm not able to reproduce the big slowdown.
I'm actually seeing IdentifyLayers to become about 15% faster in 100.2.1, and a small performance drop in IdentifyLayer at 100.3, but nothing that matches the size of performance change you're experiencing.
That leads me to believe it might be data specific - is there any chance this data could be shared with us, so we can try and reproduce?
I'm using BenchmarkDotNet to run against 38 various layers all in a local geodatabase, using the following code:
[Benchmark, System.STAThread]
public Task<int> IdentifyAllLayers()
{
return RunOnUIThread(async () =>
{
var result = await mapView.IdentifyLayersAsync(new System.Windows.Point(WindowWidth / 2, WindowHeight / 2), 10, false).ConfigureAwait(false);
if (result.Count == 0)
throw new System.Exception("Expected one layer returning");
return result.Count;
});
}
[Benchmark, System.STAThread]
public Task<int> IdentifyEachLayer()
{
return RunOnUIThread(async () =>
{
int count = 0;
foreach (var layer in map.OperationalLayers.OfType<FeatureLayer>())
{
var result = await mapView.IdentifyLayerAsync(layer, new System.Windows.Point(WindowWidth / 2, WindowHeight / 2), 10, false);
count += result.GeoElements.Count;
}
if (count == 0)
throw new System.Exception("No identify results");
return count;
});
}
Btw I suggest you use IdentifyLayersAsync to identify all layers in the map, as this seems to be a lot faster than doing an identify on each layer one by one (In my case about a factor of 10 !).
