docs: Warn about destructive performance tests

README.performance runs fio against a block device, exports LUNs, logs
in iSCSI sessions and may enable multipath. Its placeholders look
copyable, but using the wrong path or host can overwrite storage and
change both target and initiator state.

Put an explicit safety boundary before the first command. Require
authorization for the exact hosts, transports and configuration, and
allow the workflow only with verified disposable backing devices.
This commit is contained in:
Gleb Chesnokov
2026-08-21 10:05:36 +03:00
parent afa52076f3
commit 860ce48072
+5
View File
@@ -5,6 +5,11 @@ A question that is asked often is how to tune performance. This means how to
improve the IOPS and/or bandwidth measured at the initiator side. In this
README it is explained how to optimize storage performance.
WARNING: The examples below issue direct I/O, create and export LUNs, create
initiator sessions and may activate multipath. Run them only with explicit
authorization for the target and initiator hosts, transports, configuration
and disposable backing devices. Verify every placeholder before use.
Local storage
-------------
Start with measuring the performance of the local block device(s). IOPS can be