Stream end-point is very slow
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 25
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 20
Description
During the documentation meeting the Stream-locations getAll end-point with "MVP" was demoed.
The end-point was very slow. About 2 minutes for a 900k json file.
Can we verify that this slowness is caused by pl/sql and not by CDA jooq-result mapping and serialization? Perhaps this could be done by adding some metrics or via a log statement with how much time was spent in jooq execution.
Would jooq lazy streaming help?
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 at the Stream-locations getAll endpoint and measure the 900k JSON response across PL/SQL, jOOQ execution, result mapping, and serialization. The issue mentions metrics or logging for jOOQ timing; done when the main source of the delay is identified and the potential benefit of jOOQ lazy streaming is assessed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- api, backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100