Benchmark some queries on merge
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- r
- Domain
- ci-cd, data, performance
Research direction
Start by reviewing the merge workflow and the existing representative tabular and spatial query paths. The issue proposes using bench::mark to run queries after merged PRs and append timings to a CSV; done would mean a repeatable baseline, with plotting and PR benchmarking treated as stretch goals.
Written by the indexing model from the issue text.
Description
Given recent issues like #348 it might nice to have some lightweight benchmarking of a few key queries to track possible changes (either due to changes in bcdata or changes in catalogue/bcgw stuff. We can use this issue to roughgly outline a path. Here is one idea:
Lowest lift:
- Upon a merged PR, run a script that runs n number of queries for both tabular and spatial data that is representative of the types of queries that are possible with bcdata
- capture the timings on these queries with
bench::mark - appends those timings to a csv file as new rows and commit that directly into this repo
- rinse repeat to build up a baseline of how long it would take
Stretch goals:
- benchmark directly in a PR to evaluate a code before merging <- I think really this should only ever be done if we ever encounter a scenario where it would have been nice
- plot benchmarks and commit a png/svg to the repo for easy visualization.
- Dominant language
- R
- Stars
- 87
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from bcgov/bcdata
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
running air in CIOpen
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
considering enhancement wfs
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Similar issues
-
Component: R Type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/arrow#51695 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nflverse/nflverse-rosters#102 ·
-
bug priority: should
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
The-Strategy-Unit/nhp_outputs#477 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
InseeFrLab/melodi#27 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100