Skip to content

[v3] Write a brief benchmarking guide #303

Open
@SaschaMann

Description

@SaschaMann

A lot of students are interested in finding out how fast their solution runs, how they can optimize it etc. Often they use @time instead of @btime and then run into compliation times, or end up with meaningless results because the compiler treats everything as a constant.

The planned performance exercise (#353) will go into more detail but it would be good to have a very brief guide on how to benchmark one's code as part of the track docs.

Metadata

Metadata

Assignees

No one assigned

    Labels

    v3 🚀Issues that need to be resolved for the launch of v3

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions