posit-dev / posit-dev/connect-extensions
Usage Metrics Dashboard: Improve performance for large datasets
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 10
- Forks
- 8
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 1
Description
The Usage Metrics Dashboard can be slow to load large datasets. A lot of this comes from connectapi using tidyr::unnest() to parse all of Connect's responses in connectapi:::parse_connectapi(). While it would be good to come up with a general fix in connectapi, it might be good to implement a simpler workaround here, particularly as we're already doing some of the parsing of the firehose endpoint in the Shiny app currently.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in extensions/usage-metrics-dashboard and inspect how the Shiny app parses the firehose endpoint. Compare that path with connectapi:::parse_connectapi(), especially its tidyr::unnest() use. Done means the dashboard loads large datasets faster while preserving the existing usage metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- data, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100