Skip to content

Commit 5ad63c7

Browse files
committed
Fix more types, add link
1 parent 65b48e0 commit 5ad63c7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

tests/bench/transactional/results.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ Three alternatives:
66

77
1. No implicit shortcuts
88
2. Implicit shortcuts only for possible targets of megamorphic dispatch
9-
(`specializeMonoTargets` set to false)
9+
(`specializeMonoTargets` in [ShortcutImplicits.scala](../../../compiler/src/dotty/tools/dotc/transform/ShortcutImplicits.scala) set to false)
1010
3. Implicit shortcuts for all methods returning implicit function types
1111
(`specializeMonoTargets` set to true)
1212

@@ -44,7 +44,7 @@ Two benchmarks:
4444

4545
In the fully monomorphic benchmark, specializing
4646
only megamorphic targets has the same performance as
47-
not spezializing at all (not surprising, since there
47+
not specializing at all (not surprising, since there
4848
are no megamorphic targets). Specializing everything
4949
incurs about a 14% performance hit (maybe due to the extra
5050
code generated; it's hard to pin down what it is).
@@ -53,13 +53,13 @@ Note: We compute relative performance differences by comparing the
5353
second-best test runs of each series with each other.
5454

5555
In the megamorphic benchmark, it's the other way round.
56-
Specializing only megamorphic callsites leads to a performance
56+
Specializing only megamorphic call-sites leads to a performance
5757
improvement of about 36% compared to no specialization. Specializing
5858
everything leads to another 37% improvement (85% total compared
5959
to no specialization).
6060

6161
I think we need larger benchmarks to decide whether we should
62-
specicialize monomorphic call-targets or not.
62+
specialize monomorphic call-targets or not.
6363

6464
### Comparing with the Reader Monad
6565

0 commit comments

Comments
 (0)