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
Need to bench another language or framework? Open [an issue](https://github.com/CodSpeedHQ/codspeed/issues) or let us know on [Discord](https://codspeed.io/discord)!
83
+
67
84
## Advanced usage
68
85
69
86
### Installing tools before running
@@ -76,14 +93,6 @@ codspeed setup
76
93
77
94
This is especially useful when configuring environments with tools such as docker.
78
95
79
-
### Logging level
80
-
81
-
Use the `CODSPEED_LOG` environment variable to set the logging level:
82
-
83
-
```bash
84
-
CODSPEED_LOG=debug codspeed run ...
85
-
```
86
-
87
96
### Changing the mode of the runner
88
97
89
98
By default, the runner will run the benchmark in the `simulation` mode. You can specify the mode with the `--mode` flag of the `run` command:
@@ -97,6 +106,5 @@ codspeed run --mode walltime <my-benchmark-command>
97
106
```
98
107
99
108
> [!WARNING]
100
-
> We strongly recommend not changing this mode unless you know what you are doing.
101
109
> Using the `walltime` mode on traditional VMs/Hosted Runners will lead to inconsistent data. For the best results, we recommend using CodSpeed Hosted Macro Runners, which are fine-tuned for performance measurement consistency.
102
110
> Check out the [Walltime Instrument Documentation](https://docs.codspeed.io/instruments/walltime/) for more details.
0 commit comments