-
Notifications
You must be signed in to change notification settings - Fork 0
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
Performance! #20
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
Currently the work stealing scheduler has very odd scaling characteristics. I will place a * that these numbers are not realistic for a real application, since a real application would probably have more then a nop as a task. But still, the scheduler does not scale as well as I would have hoped.
1 thread
4 threads
12 threads
A few of the tests are basically benchmarks of spawning threads
start_die, chain_10_use_die
for example.It worries me that
bench_fibb_steal
gets worse as threads are added (it should be very parallel). Andrepeat_1_000_x_1_000
is at best a 3 times increase.The text was updated successfully, but these errors were encountered: