Performance of Croissant with reviews (JSON is not cached)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
In #12425 we've implemented Local Reviews (via API and Croissant) but there are performance problems that we are deferring until the following issue (a dependency) can be worked on:
In its absence (as of #12425), we adding a "reviews" array to Croissant JSON on the fly, bypassing our usual pattern of caching the export format to disk and reading from that.
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 by reviewing #12425 and the linked dataverse-spi issue #5 to understand the Local Reviews and Croissant export paths. Trace where the reviews array is added to Croissant JSON and how other export formats are cached to disk; done means the reviews data uses the normal cache path without the current performance problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100