perf(api): batch APIs queries to request for maximum number of datapo…

[chejimmy]

…ints

What this PR does / why we need it:

Grafana has a default behavior to set query's maxDataPoints to a somewhat low number (compares to the SiteWise APIs maximum), and causes unnecessary pagination for queries with high response data points. It creates unnecessary latency and request (TPS) load to the server.

For example, for 6 hour time range - the maxDataPoints is auto set to ~500, and requires ~50 request for 6 hours of 1 second data points = 6hr60min/hr60sec/min / 432maxDataPoints/request.

This PR updates the batch APIs queries to request for maximum number of datapoints the SiteWise APIs can support for a better UX.

• BatchGetAssetPropertyValueHistoryMaxResults of 20000
• BatchGetAssetPropertyAggregatesMaxResults of 4000

Before this PR - GetPropertyValueHistory for 6 hr took ~10 seconds:

Screen.Recording.2024-05-04.at.1.19.07.AM.1080p.mov

After this PR - GetPropertyValueHistory for 6 hr took ~1.5 seconds:

Screen.Recording.2024-05-04.at.1.16.41.AM.mov

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

[iwysiu]

Hi @chejimmy ! Overall looks good and makes sense to me, but I think you need to add "datapoints" to the words section in cspell.config.json to pass the spell check (and the ci). You can double check it locally by running yarn spellcheck

[tracy-french]

Awesome! This looks like a huge performance boost!

[chejimmy]

Hi @chejimmy ! Overall looks good and makes sense to me, but I think you need to add "datapoints" to the words section in cspell.config.json to pass the spell check (and the ci). You can double check it locally by running yarn spellcheck

I see; updated to data points instead to conform to the existing spelling 👍