If you have enabled the option "Complete current transaction for stopped virtual users" at SETTINGS | ACTIVE PROFILE | SIMULATION, then this allows a stopped virtual user to complete the active transaction before stopping. With this setting enabled a virtual user checks whether to stop only at the beginning of a new transaction, and so the active transaction must be completed before the user will stop. If this option is disabled, the virtual user checks whether to stop during thinking and waiting times, during the times in the waiting queue, at the beginning of each transaction and after any API function. This explains the delay in stopping all users even with this option disabled. An alternative to using the "stop" option is to use the "kill" option. When using the "kill" option: * Each virtual user stops immediately. * All results data collected up to this point are valid and available. * The "Complete current transaction for stopped virtual user" and "Call end transaction for stopped virtual users" settings have no effect. See also: What is the difference between the Stop, Kill and Abort commands when stopping a loadtest?
↧