Slow response times

[Benedikt Sutter]

Hey,

I've noticed some really slow response times in the last few days when using the `identify` endpoint for the ch.bfe.solarenergie-eignung-daecher layer and the `limit` keyword set, e.g.

https://api3.geo.admin.ch/rest/services/api/MapServer/identify?geometry=501048.564,113869.963&geometryFormat=geojson&geometryType=esriGeometryPoint&imageDisplay=653,644,96&layers=all:ch.bfe.solarenergie-eignung-daecher&mapExtent=501019.227,113837.867,501087.963,113903.229&returnGeometry=True&sr=21781&limit=10&tolerance=1

This call now takes around 4 - 10 seconds to return, it used to be a few ms. If I omit the `limit` keyword, we're down to around ~1s.

I've checked out this request and the corresponding github issue, which makes me think this could be some sort of indexing issue as well?

Cheers & thanks

[David...@swisstopo.ch]

We will look into this via

https://github.com/geoadmin/mf-chsdi3/issues/3612

--
You received this message because you are subscribed to the Google Groups "GeoAdmin API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geoadmin-api...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/geoadmin-api/76d80df9-913d-4075-b0cd-dbaaad9a815an%40googlegroups.com.

[Benedikt Sutter]

Thanks for the update!

[Benedikt Sutter]

Thanks for looking into this, i've checked out the issue & fix on GitHub, the query is way faster now.

However, I'm wondering whether there's an index missing in the DB, if I query

https://api3.geo.admin.ch/rest/services/api/MapServer/identify?geometry=501048.564,113869.963&geometryFormat=geojson&geometryType=esriGeometryPoint&imageDisplay=653,644,96&layers=all:ch.bfe.solarenergie-eignung-daecher&mapExtent=501019.227,113837.867,501087.963,113903.229&returnGeometry=True&sr=21781&limit=1&tolerance=1

with an arbitrary point as geometry parameter, the first call takes anywhere between 5s - Guru meditation. All subsequent calls for the exact same point take around 15ms. If you change the point slightly (even increase or decrease one single digit after the decimal point), the call again takes > 5s. Subsequent calls then again again take ~15ms. I'm testing this with Postman, so I don't expect local caching to be the source of this weird behaviour. I also tested it across several browsers, i.e. make the first call on browser A, wait 5s until it returns. Do calls 2-n on browser B, admire the 15ms.

[GeoAdminCh API]

As mentioend in https://github.com/geoadmin/mf-chsdi3/issues/3612#issuecomment-778158365  related to postgresql  stack. A work aroudn has been proposed