Determine Measurement Limit for new Data Explorer
- Dominant language
- TypeScript
- Stars
- 117
- Forks
- 51
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 4
Description
## Spike Description
In the old data explorer, there was a hard limit of 200 or 500 entries in the measurement list, depending on a feature flag setting.
We can assume this was done because of performance and the impact of gathering a large list and all the associated metadata.
With the performance improvements that have been made in both back-end and front-end and with the different way we are handing metaqueries, we should determine if this limit is still necessary, and if so - what limit is feasible.
It certainly *seems* like we could show more than 200 entries without it being problematic.
This spike is for doing some testing and analysis to determine what our options might be here.
## Deliverable
- Recommendation on what (if any) limit can be put on the measurement list in the new data explorer
##
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.