Performance issues with XLocate 2
Posted: Fri Mar 06, 2020 1:19 pm
Hello,
we have a performance problem with the XLocate 2 API
We have a list of ~1000 addresses that we are geocoding for testing, and PTV2 performs significantly worse than PTV1.
The average time needed for an address is ~200ms for version 1 and 1 second (970ms) for version 2.
We noticed that version 2 returns much more results than version 1 (about 10 times as many). We suspect that one factor of the performance problem lies there.
How can we improve the performance of version 2? Is it possible to limit the maximum number of results?
we have a performance problem with the XLocate 2 API
We have a list of ~1000 addresses that we are geocoding for testing, and PTV2 performs significantly worse than PTV1.
The average time needed for an address is ~200ms for version 1 and 1 second (970ms) for version 2.
We noticed that version 2 returns much more results than version 1 (about 10 times as many). We suspect that one factor of the performance problem lies there.
How can we improve the performance of version 2? Is it possible to limit the maximum number of results?