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
benchmark_report.log() # or print(benchmark_report)
149
-
150
144
# convert artifacts to a dictionary or dataframe
151
145
benchmark_config.to_dict() # or benchmark_config.to_dataframe()
152
146
@@ -175,15 +169,17 @@ If you're on VSCode, you can hover over the configuration classes to see the ava
175
169
You can also run a benchmark using the command line by specifying the configuration directory and the configuration name. Both arguments are mandatory for [`hydra`](https://hydra.cc/). `--config-dir` is the directory where the configuration files are stored and `--config-name` is the name of the configuration file without its `.yaml` extension.
This will run the benchmark using the configuration in [`examples/pytorch_bert.yaml`](examples/pytorch_bert.yaml) and store the results in `runs/pytorch_bert`.
175
+
This will run the benchmark using the configuration in [`examples/cuda_pytorch_bert.yaml`](examples/cuda_pytorch_bert.yaml) and store the results in `runs/cuda_pytorch_bert`.
182
176
183
177
The resulting files are :
184
178
185
179
-`benchmark_config.json` which contains the configuration used for the benchmark, including the backend, launcher, scenario and the environment in which the benchmark was run.
186
180
-`benchmark_report.json` which contains a full report of the benchmark's results, like latency measurements, memory usage, energy consumption, etc.
181
+
-`benchmark_report.txt` which contains a detailed report of the benchmark's results, in the same format they were logged.
182
+
-`benchmark_report.md` which contains a detailed report of the benchmark's results, in markdown format.
187
183
-`benchmark.json` contains both the report and the configuration in a single file.
188
184
-`benchmark.log` contains the logs of the benchmark run.
189
185
@@ -309,9 +305,7 @@ For more information on the features of each backend, you can check their respec
0 commit comments