Skip to content

Add a real benchmark-alteration test #480

Description

@fbusato

The goal is to introduce an actual performance change, rather than editing benchmark output.

performance change could rely on:

  • debug versus release builds
  • artificial memory accesses
  • compiler flags

(see parent issue)
Verify that the comparison script detects the expected FAST or SLOW outcomes.

Activity

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

    No labels
    No labels

    Type

    No type

    Projects

    • Status
      Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions