Describe the feature you'd like and what it will do
The SensorThings API currently calculates a count value for all GET requests. The count only needs to be calculated if a user asks for it to be included in the SensorThings response.
Why is this feature important?
The auth-filtered count calculation on the full Observations table is fairly CPU intensive and can cause paginated requests on the Observations endpoint without the count value included to take several seconds even for a small subset of data. Ignoring the count unless the user requests it speeds up this query significantly.
Is your feature request related to a problem? Please describe.
kjlippold
commented
8 months ago
Describe the feature you'd like and what it will do
The SensorThings API currently calculates a count value for all GET requests. The count only needs to be calculated if a user asks for it to be included in the SensorThings response.
Why is this feature important?
The auth-filtered count calculation on the full Observations table is fairly CPU intensive and can cause paginated requests on the Observations endpoint without the count value included to take several seconds even for a small subset of data. Ignoring the count unless the user requests it speeds up this query significantly.
Is your feature request related to a problem? Please describe.
No response
Any additional comments?
No response