Slonik is 50x slower when used with ncc
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
Slonik is 10x slower when I compiled my code using ncc. I'm not sure where the issue lies, because pg does not have the same issue.
Here is a minimal repo to reproduce the issue https://github.com/thomasthiebaud/slonik-perf-issue
Contributor guide
No contributing guide indexed for this repository
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 running the linked minimal repository, comparing Slonik performance in ncc-compiled output with the uncompiled version and with pg. Trace the slowdown through ncc's compilation path and identify what causes the discrepancy; done means the compiled Slonik case no longer exhibits the reported severe regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system, performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100