You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-13Lines changed: 5 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,14 +6,6 @@ Solutions for [Advent of Code](https://adventofcode.com/) in [Rust](https://www.
6
6
7
7
<!--- advent_readme_stars table --->
8
8
9
-
<!--- benchmarking table --->
10
-
## Benchmarks
11
-
12
-
| Day | Part 1 | Part 2 |
13
-
| :---: | :---: | :---: |
14
-
|[Day 9](./src/bin/09.rs)|`19.0ns`|`19.0ns`|
15
-
16
-
**Total: 0.00ms**
17
9
<!--- benchmarking table --->
18
10
19
11
---
@@ -124,15 +116,15 @@ cargo all
124
116
# Total: 0.20ms
125
117
```
126
118
127
-
This runs all solutions sequentially and prints output to the command-line. Same as for the `solve` command, the `--release` flag runs an optimized build.
119
+
This runs all solutions sequentially and prints output to the command-line. Same as for the `solve` command, the `--release` flag runs an optimized build and the `--time` flag outputs benchmarks.
128
120
129
-
####Update readme benchmarks
121
+
###➡️ Update readme benchmarks
130
122
131
-
The template can output a table with solution times to your readme.
123
+
The template can write benchmark times to the README via the `cargo time` command.
132
124
133
-
In order to generate the benchmarking table, run `cargo time`. By default, this command checks for missing benchmarks, runs those solutions, and then updates the table. If you want to (re-)time all solutions, run `cargo time --force` flag. If you want to (re-)time a specific solution, run `cargo time <day>`.
125
+
By default, this command checks for missing benchmarks, runs those solutions, and then updates the table. If you want to (re-)time all solutions, run `cargo time --all`. If you want to (re-)time one specific solution, run `cargo time <day>`.
134
126
135
-
Please note that these are not "scientific" benchmarks, understand them as a fun approximation. 😉 Timings, especially in the microseconds range, might change a bit between invocations.
127
+
Please note that these are not _scientific_ benchmarks, understand them as a fun approximation. 😉 Timings, especially in the microseconds range, might change a bit between invocations.
0 commit comments