Even if, as shown in the previous section, the final configuration is part of the report, it will not prevent you from propagating all the good practices you deduced from the benchmark in the code base. The goal is to reduce the mandatory configuration.
For instance, if you identified that you need a timeout of 1 second instead of the default 30 seconds to have a good performance, updating your defaults to 1 second directly in the code base will avoid having a bad performance if the configuration is forgotten. This part is a trade-off between default usability and performance, but generally you can still enhance the default user/operation team experience by doing it.
If you have some provisioning recipes ...
