What happens when you set --threads to a number greater than your database allows?

Setting the --threads option to a number greater than what your database allows means that only the maximum number of threads permitted by the database will be utilized during execution. The system effectively caps the number of concurrent processes to adhere to the limits set by the database settings. This ensures that the database does not become overwhelmed and can handle the queries efficiently within its operational constraints.

The other options suggest unrealistic scenarios. Ignoring all threads would render the command ineffective, while immediate execution failure implies a lack of any possible threading operation. The idea of improved performance beyond the database's limits contradicts the fundamental principles of concurrent processing, where exceeding capacity can lead to resource contention rather than enhanced throughput. Therefore, only the allowed number of threads will run, aligning with the database’s configured limits.