# Any limitations with distributed load-drivers?

**URL:** <https://discuss.elastic.co/t/any-limitations-with-distributed-load-drivers/107939>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [November 16, 2017, 12:59pm UTC](https://discuss.elastic.co/t/any-limitations-with-distributed-load-drivers/107939 "2017-11-16T12:59:07Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [November 22, 2017, 11:53am UTC](https://discuss.elastic.co/t/any-limitations-with-distributed-load-drivers/107939/11 "2017-11-22T11:53:09Z")

</div>

> [@JohanRask](#):
>
> When using distributed load drivers, is this the total number of clients or is this the number of clients on each machine?

The track specification is independent whether the load driver runs on one or multiple hosts. In other words: It's the total number of clients.

Glad that you managed to scale it. Although I have to admit 132 clients indexing at maximum speed concurrently is quite a high number. 🙂

---

_[View the full topic](https://discuss.elastic.co/t/any-limitations-with-distributed-load-drivers/107939)._