Greenstand / Greenstand/treetracker-testing
Test and report the performance difference between original query api and denormalized query api
Open
good first issue
k6
pressure-test
test-engineering
- Dominant language
- No language data
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We are developing the `denormalized` query api, the story is [here](https://docs.greenstand.org/web-map/denormalized-map-data), now we need to test the improvement of the new API.
The idea is to use k6 to press the test env (https://test-k8s.treetracker.org/query/ and https://test-k8s.treetracker.org/alpha/query/), but any other suggestions are welcome.
Please give a plan for this and design the report of this test.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.