# Concurrent requests In [[Load Testing]], [[Request|requests]] are concurrent (sometimes called "parallel") if they are executed simultaneously instead of sequentially. In the same way that decreasing [[Dynamic think time and pacing|Think Time]] increases how many requests a user can make in a certain amount of time, using concurrent requests [[Increasing throughput of a load test|increases throughput]] because the requests are made in batches. Using concurrent requests can [[Making load testing scripts more realistic|make tests more realistic]] because web browsers send some requests concurrently by default, such as embedded resources on a page. Determine how API calls are made in production: are they usually called one after another (sequential) or made at the same time (concurrent)? This will determine whether you incorporate concurrent requests in your script. ## In [[Load Testing Tool]]s ### [[JMeter Concurrent requests|Concurrent requests in JMeter]] ### [[Concurrent requests in Gatling]] ### [[Parallel requests in k6]]