-
Notifications
You must be signed in to change notification settings - Fork 529
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ParallelBenchmark #2167
Add ParallelBenchmark #2167
Conversation
Outstanding! If I may ask, how many physical threads does your machine have? ( Edit: Oh, reading. :-D |
^ Just updated the machine details |
benchmarks/src/main/scala/cats/effect/benchmarks/ParallelBenchmark.scala
Outdated
Show resolved
Hide resolved
I'm running the benchmark too, I will post base results. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hold on merging this. Some changes @manufacturist and I discussed directly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting for discussed changes then.
Ran the benchmark with cpuTokens values
[info] Benchmark (cpuTokens) (size) Mode Cnt Score Error Units
[info] ParallelBenchmark.parTraverse 100 100 thrpt 20 6487.985 ± 251.364 ops/s
[info] ParallelBenchmark.parTraverse 100 1000 thrpt 20 791.526 ± 6.699 ops/s
[info] ParallelBenchmark.parTraverse 100 10000 thrpt 20 75.203 ± 0.372 ops/s
[info] ParallelBenchmark.parTraverse 1000 100 thrpt 20 4505.063 ± 170.821 ops/s
[info] ParallelBenchmark.parTraverse 1000 1000 thrpt 20 545.267 ± 3.686 ops/s
[info] ParallelBenchmark.parTraverse 1000 10000 thrpt 20 58.031 ± 4.109 ops/s
[info] ParallelBenchmark.parTraverse 10000 100 thrpt 20 2294.218 ± 7.110 ops/s
[info] ParallelBenchmark.parTraverse 10000 1000 thrpt 20 237.894 ± 1.132 ops/s
[info] ParallelBenchmark.parTraverse 10000 10000 thrpt 20 22.876 ± 0.288 ops/s
[info] ParallelBenchmark.parTraverse 100000 100 thrpt 20 320.065 ± 0.294 ops/s
[info] ParallelBenchmark.parTraverse 100000 1000 thrpt 20 32.039 ± 0.173 ops/s
[info] ParallelBenchmark.parTraverse 100000 10000 thrpt 20 3.186 ± 0.040 ops/s
[info] ParallelBenchmark.parTraverse 1000000 100 thrpt 20 33.128 ± 0.042 ops/s
[info] ParallelBenchmark.parTraverse 1000000 1000 thrpt 20 3.318 ± 0.008 ops/s
[info] ParallelBenchmark.parTraverse 1000000 10000 thrpt 20 0.351 ± 0.035 ops/s
[info] ParallelBenchmark.traverse 100 100 thrpt 20 68114.475 ± 750.640 ops/s
[info] ParallelBenchmark.traverse 100 1000 thrpt 20 8024.076 ± 104.133 ops/s
[info] ParallelBenchmark.traverse 100 10000 thrpt 20 918.410 ± 4.294 ops/s
[info] ParallelBenchmark.traverse 1000 100 thrpt 20 15431.432 ± 32.394 ops/s
[info] ParallelBenchmark.traverse 1000 1000 thrpt 20 1615.529 ± 19.228 ops/s
[info] ParallelBenchmark.traverse 1000 10000 thrpt 20 166.345 ± 0.537 ops/s
[info] ParallelBenchmark.traverse 10000 100 thrpt 20 1766.005 ± 7.986 ops/s
[info] ParallelBenchmark.traverse 10000 1000 thrpt 20 178.010 ± 0.157 ops/s
[info] ParallelBenchmark.traverse 10000 10000 thrpt 20 17.718 ± 0.106 ops/s
[info] ParallelBenchmark.traverse 100000 100 thrpt 20 179.566 ± 0.178 ops/s
[info] ParallelBenchmark.traverse 100000 1000 thrpt 20 17.847 ± 0.110 ops/s
[info] ParallelBenchmark.traverse 100000 10000 thrpt 20 1.728 ± 0.061 ops/s
[info] ParallelBenchmark.traverse 1000000 100 thrpt 20 17.867 ± 0.094 ops/s
[info] ParallelBenchmark.traverse 1000000 1000 thrpt 20 1.717 ± 0.084 ops/s
[info] ParallelBenchmark.traverse 1000000 10000 thrpt 20 0.178 ± 0.006 ops/s
|
Excellent. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Outstanding! That's actually more data points than I was expecting. 🙂 This is going to be super useful for some other changes as well, thank you!
5d9eca0
to
3076baa
Compare
Thank you @manufacturist! Great work. |
As requested by @vasilmkd, moved the
ParallelBenchmark
to a new PR. The reason for the 6 benchmarks is to compare the performance ofparTraverse
vstraverse
under different CPU load.Posted the benchmarks for the
series/3.x
:LE:
Executing Machine Details