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: content/learning-paths/servers-and-cloud-computing/bolt-merge/how-to-2.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ Before running the workload, you might need to initialize a new data directory i
106
106
bin/mysqld --initialize-insecure --datadir=data
107
107
```
108
108
109
-
Start the instrumented server. On an 8-core system, use core 2 for mysqld and core 7 for sysbench to avoid contention.
109
+
Start the instrumented server. On an 8-core system, use core 2 for mysqld and core 7 for Sysbench to avoid contention.
110
110
111
111
Run the command from build directory:
112
112
@@ -171,15 +171,15 @@ You only need to do this once. Don’t repeat it before each test.
171
171
172
172
## Reset the database between runs
173
173
174
-
This clears all existing tables and data from the bench database, giving you a clean slate for sysbench prepare without needing to recreate the user or reinitialize the datadir.
174
+
This clears all existing tables and data from the bench database, giving you a clean slate for Sysbench prepare without needing to recreate the user or reinitialize the datadir.
Use `./src/sysbench` for running benchmarks unless installed globally.
194
194
195
-
## Prepare the dataset with sysbench
195
+
## Prepare the dataset with Sysbench
196
196
197
197
Run `sysbench` with the `prepare` option:
198
198
@@ -263,7 +263,7 @@ Start the MySQL instrumented binary in first terminal.
263
263
264
264
Use a workload generator to stress the binary in a feature-specific way.
265
265
266
-
For example, to simulate **read-only traffic** with sysbench:
266
+
For example, to simulate **read-only traffic** with Sysbench:
267
267
268
268
```bash
269
269
taskset -c 7 ./src/sysbench \
@@ -294,7 +294,7 @@ On an 8-core system, cores are numbered 0-7. Adjust the `taskset -c` values as n
294
294
295
295
The `.fdata` file defined in `--instrumentation-file` will be populated with runtime execution data.
296
296
297
-
After completing each benchmark run (for example, after sysbench run), you must cleanly shut down the MySQL server and reset the dataset to ensure the next test starts from a consistent state.
297
+
After completing each benchmark run (for example, after Sysbench run), you must cleanly shut down the MySQL server and reset the dataset to ensure the next test starts from a consistent state.
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/bolt-merge/how-to-5.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ Second test run:
53
53
| Total time (s) | 239.8 | 239.72 | 239.9 | 239.9 | 239.9 |
54
54
55
55
{{% notice Note %}}
56
-
All sysbench and .fdata file paths, as well as taskset usage, should match the conventions in previous steps: use sysbench from PATH (no src/), use /usr/share/sysbench/ for Lua scripts, and use $HOME-based paths for all .fdata and library files. On an 8-core system, use taskset -c 7 for sysbench and avoid contention with mysqld.
56
+
All Sysbench and .fdata file paths, as well as taskset usage, should match the conventions in previous steps: use Sysbench from PATH (no src/), use /usr/share/sysbench/ for Lua scripts, and use $HOME-based paths for all .fdata and library files. On an 8-core system, use taskset -c 7 for Sysbench and avoid contention with mysqld.
0 commit comments