Skip to content

Benchmark code for the runtime #8339

Closed
Closed
@toddaaro

Description

@toddaaro
Contributor

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.

Activity

toddaaro

toddaaro commented on Aug 17, 2013

@toddaaro
ContributorAuthor

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

thestinger commented on Sep 19, 2014

@thestinger
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

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @toddaaro@thestinger

        Issue actions

          Benchmark code for the runtime · Issue #8339 · rust-lang/rust