typelevel / typelevel/cats-effect
Do more benchmarking on ScalaJS tracing
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
It's important to convince ourselves that we haven't somehow entirely destroyed performance on scalajs. The benchmark results are really inconsistent and it would be immensely helpful if someone who understands V8 and some of ScalaJS were able to help out on this a bit, since it's difficult to explain the numbers we're seeing in #2207.
Running hey benchmarks on http4s-server and even perhaps the Fs2 benchmarks on ScalaJS would probably be the best way to start to get some confidence over how this change manifests in realistic workloads.
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 the change and benchmark results referenced in #2207, then run the hey benchmarks on http4s-server and, if useful, the Fs2 benchmarks on ScalaJS. Compare the results across runs and realistic workloads, focusing on V8 and ScalaJS tracing. Done means the inconsistent numbers are characterized well enough to assess whether performance was substantially damaged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100