# Why is no warmup defined in event-data-track challenge elasticlogs-querying

**URL:** <https://discuss.elastic.co/t/why-is-no-warmup-defined-in-event-data-track-challenge-elasticlogs-querying/177015>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [April 16, 2019, 7:40am UTC](https://discuss.elastic.co/t/why-is-no-warmup-defined-in-event-data-track-challenge-elasticlogs-querying/177015 "2019-04-16T07:40:50Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)\
**Post date:** [April 16, 2019, 7:40am UTC](https://discuss.elastic.co/t/why-is-no-warmup-defined-in-event-data-track-challenge-elasticlogs-querying/177015/1 "2019-04-16T07:40:50Z")

</div>

Hi @Christian_Dahlqvist / @danielmitterdorfer,

I made quite some tests with the event-data-track.

My testrun was like the following:

- restart elasticsearch
- import 250 mio events via challenge [elasticlogs-1bn-load](https://github.com/elastic/rally-eventdata-track/blob/master/eventdata/challenges/elasticlogs-1bn-load.json)
- do this 3x
  - restart elasticsearch
  - run challenge [elasticlogs-querying](https://github.com/elastic/rally-eventdata-track/blob/master/eventdata/challenges/elasticlogs-querying.json).

- do this 5x
  - restart elasticsearch
  - run challenge [combined-indexing-and-querying](https://github.com/elastic/rally-eventdata-track/blob/master/eventdata/challenges/combined-indexing-and-querying.json)

- do this 2x
  - restart elasticsearch
  - run challenge [elasticlogs-querying]([https://github.com/elastic/rally-eventdata-](https://github.com/elastic/rally-eventdata-)

When I check the service time of kibana queries during elasticlogs-querying I can see a massive spike at the beginning.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/b/1b869e38fc9482c45ba4b752473970e4834df16d.png)  
The image shows the service time of the 1st three iterations of elasticlogs-querying.

For me it looks like some warmup issue which occurs after massive writing. (maybe disk cache by OS?).

I just want to ask, why the warmup period is explicitly set to 0.

```
   {
      "parallel": {
        "warmup-time-period": 0,
        "time-period": 1800,
        "clients": 4,
        "tasks": [
          {
            "operation": "relative-kibana-content_issues-dashboard_50%",
            "target-interval": 30
          },
          {
            "operation": "relative-kibana-content_issues-dashboard_75%",
            "target-interval": 90
          },
          {
            "operation": "relative-kibana-traffic-dashboard_50%",
            "target-interval": 40
          },
          {
            "operation": "relative-kibana-discover_50%",
            "target-interval": 60
          }
        ]
      } 

```

Is there a deeper meaning behind that? What is it? I just would like to understand the decision 😉

Regards, Andreas

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 7, 2019, 5:53am UTC](https://discuss.elastic.co/t/why-is-no-warmup-defined-in-event-data-track-challenge-elasticlogs-querying/177015/2 "2019-05-07T05:53:50Z")

</div>

If I remember correctly I explicitly set it that way as I wanted to see all data points. As you correctly point out having a short warmup might have been a good idea.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 4, 2019, 5:53am UTC](https://discuss.elastic.co/t/why-is-no-warmup-defined-in-event-data-track-challenge-elasticlogs-querying/177015/3 "2019-06-04T05:53:52Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.