typelevel / typelevel/cats-effect
"are source maps just… really really really slow?"
Open
Nobody has claimed this yet.
:mushroom: enhancement
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Running the tracing example from the docs on Node.js with the exact same tracing parameters.
https://typelevel.org/cats-effect/docs/tracing#complete-code
CATS_EFFECT_TRACING_BUFFER_SIZE=64 CATS_EFFECT_TRACING_MODE=FULL node --enable-source-maps example/js/target/scala-2.13/cats-effect-example-fastopt/main.js
With sourcemaps:
real 0m4.981s
user 0m4.218s
sys 0m1.119s
Without:
real 0m0.169s
user 0m0.152s
sys 0m0.025s
One idea is to provide tooling/utility that takes unsourcemapped exceptions + a sourcemap and provides sourcemapped exceptions.
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 tracing example in the linked documentation and run the provided Node.js command with and without --enable-source-maps to reproduce the timing difference. Done means identifying the source of the slowdown and determining whether the proposed utility for sourcemapping exceptions is viable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, scala
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100