The Gatling load test has a loops option which is the number of requests per client. This affects the overall duration of the test but does not provide any guarantees around how long the test will execute. There are scenarios in which it would be useful to be able to specify the test duration. For example, I am currently trying to do some testing with the compression job. I want the Gatling test to run long enough to ensure that the compression job runs a certain number of times. Having a duration parameters makes this a lot easier to do.