# Premature end of Benchmark run

**URL:** <https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [October 4, 2017, 10:53am UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684 "2017-10-04T10:53:11Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [October 5, 2017, 1:04pm UTC](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684/5 "2017-10-05T13:04:40Z")

</div>

Hi @sanketshinde,

how long did the benchmark take in total? Depending on the machines that you're running on and the document structure, it can easily happen that a 10GB document corpus is too small.

For testing you can try to set `warmup-time-period` to 0. Then, Rally will not do any warmup and you should see samples.

Daniel

---

_[View the full topic](https://discuss.elastic.co/t/premature-end-of-benchmark-run/102684)._
