Investigate TPC-DS performance regression
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.9k
- Forks
- 342
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 53
Description
Environment
This issue was introduced by a specific commit. (The original content mentions a mapping relationship for "Target Branch" and "Iteration" attributes, but no specific version numbers, build times, or commit hashes are provided in the given text.)
Description / Steps to Reproduce
A performance regression has been identified in TPC-DS benchmarks. The detailed performance report is available at the following internal link:
http://:9090/jenkins/view/opensource_lite/job/lite_perf_guard/ws/performance_report.html
An image from the performance report is referenced below:
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 with the internal performance_report.html linked in the issue and identify the regressing TPC-DS benchmark. Trace the change back to the introducing commit, reproduce the regression, and document or resolve its cause; the issue provides no named source file or test beyond the report.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- databases, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100