Skip to content

Benchmark code for the runtime #8339

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

Closed
toddaaro opened this issue Aug 6, 2013 · 2 comments
Closed

Benchmark code for the runtime #8339

toddaaro opened this issue Aug 6, 2013 · 2 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@toddaaro
Copy link
Contributor

toddaaro commented Aug 6, 2013

We need a solid suite of simple benchmarks so we can evaluate the performance of the runtime. On the simple side benchmarks for raw spawn performance and raw message sending are great. The "more complicated" benchmarks should be simple programs that are frequently benchmarked in other parallelism systems. Parfib, k-means, etc.

@toddaaro
Copy link
Contributor Author

Currently we have a spawn benchmark, a parfib benchmark, and a ping-pong message passing benchmark. A start but we need expansion. Benchmarks targeted at the runtime are in the bench folder, and names start with "rt-".

@thestinger
Copy link
Contributor

There are a lot of benchmarks now, and since green threads are being removed as part of #17325 I don't think there's going to be much to do that's interesting. It will just perform as well as the native building blocks provided by the platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

2 participants