# No Median CPU Usage in my track results

**URL:** <https://discuss.elastic.co/t/no-median-cpu-usage-in-my-track-results/89284>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [June 13, 2017, 11:22pm UTC](https://discuss.elastic.co/t/no-median-cpu-usage-in-my-track-results/89284 "2017-06-13T23:22:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bernitorres](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bernitorres/32/19099_2.png) [@bernitorres](https://discuss.elastic.co/u/bernitorres)\
**Post date:** [June 13, 2017, 11:22pm UTC](https://discuss.elastic.co/t/no-median-cpu-usage-in-my-track-results/89284/1 "2017-06-13T23:22:23Z")

</div>

Hello,

I created 3 different tracks to compare the results of some mapping changes. Out of these 3 tracks, only one of these doesn't report the Median CPU Usage. The metric is not reported at all, not even with a blank value.

What could be the reason that CPU usage is in the other 2 track results but not this one?

I am indexing 10 million documents  
esrally 0.5.3

> esrally race --track=flat --distribution-version=1.7.3

| Lap | Metric | Operation | Value | Unit |
| --- | --- | --- | --- | --- |
| All | Indexing time | | 0.19725 | min |
| All | Refresh time | | 0.0711167 | min |
| All | Median CPU usage | | 97.9 | % |
| All | Total Young Gen GC | | 0.635 | s |
| All | Total Old Gen GC | | 0.068 | s |
| All | Index size | | 0.0413944 | GB |
| All | Totally written | | 0.116398 | GB |
| All | Heap used for segments | | 0.352222 | MB |
| All | Segment count | | 22 | |
| All | Min Throughput | index-append | 1365.1 | docs/s |
| All | Median Throughput | index-append | 1365.1 | docs/s |
| All | Max Throughput | index-append | 1365.1 | docs/s |
| All | 100th percentile latency | index-append | 7116.46 | ms |
| All | 100th percentile service time | index-append | 7116.46 | ms |
| All | error rate | index-append | 0 | % |

.....

---

<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:** [June 19, 2017, 6:34am UTC](https://discuss.elastic.co/t/no-median-cpu-usage-in-my-track-results/89284/2 "2017-06-19T06:34:26Z")

</div>

Hi @bernitorres,

Based on the metrics I see here (e.g. index size is just 40 MB) I guess that your benchmark does not take very long and sometimes even finishes within the warmup period. Rally will not include any warmup samples in the final report and that may be the reason why you do not see any CPU usage results.

If you store your metrics in a dedicated Elasticsearch metrics store, it will contain all raw samples and you could run a query to check this. You could also (temporarily) set the [warmup time period](http://esrally.readthedocs.io/en/stable/track.html#time-based-vs-iteration-based) of the bulk-index operation in your track to `0` to check my assumption. However, I suggest to index more documents as you're basically only measuring Elasticsearch's warmup behavior.

Daniel

---

<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:** [July 17, 2017, 6:34am UTC](https://discuss.elastic.co/t/no-median-cpu-usage-in-my-track-results/89284/3 "2017-07-17T06:34:29Z")

</div>

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