# Showing TPS on line visulaize

**URL:** <https://discuss.elastic.co/t/showing-tps-on-line-visulaize/286898>\
**Category:** Kibana\
**Created:** [October 16, 2021, 4:58pm UTC](https://discuss.elastic.co/t/showing-tps-on-line-visulaize/286898 "2021-10-16T16:58:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Marta\_Bondyra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marta_bondyra/32/102122_2.png) [@Marta\_Bondyra](https://discuss.elastic.co/u/Marta_Bondyra)\
**Post date:** [October 20, 2021, 8:26am UTC](https://discuss.elastic.co/t/showing-tps-on-line-visulaize/286898/2 "2021-10-20T08:26:39Z")

</div>

Hi @sahere37 ,

In Kibana, you can only define minimum interval - most of the time it works fine for the timeranges chosen, but not always. So for example, if your timerange is 1 hour, and you've defined minimum interval of 1s, you will get 3600 buckets of data. If you have timerange of 1 month, you would get over 2 million buckets if the interval is precise. This is a performance issue for ES and kibana and that's why the interval used will be much bigger than the minimum, to not create so many buckets.

However, if what interests you is the actual speed of data/timeunit, you can use Lens visualization with `Normalize by unit` setting. That would give you the 'speed' of your data per chosen unit and doesn't depend on the chosen/calculated interval. Let me know if that helps!

 ![Screenshot 2021-10-20 at 10.26.01](https://us1.discourse-cdn.com/elastic/original/3X/8/0/80f4c0e3bf24ca61626bdc9a24ddcf7ced3aa05d.png)

 ![Screenshot 2021-10-20 at 10.26.10](https://us1.discourse-cdn.com/elastic/original/3X/3/5/3521efef9d75633b7cb753c8b260d374f8767594.png)

 ![Screenshot 2021-10-20 at 10.26.20](https://us1.discourse-cdn.com/elastic/original/3X/e/0/e0aadfa4a9e4d9a8746744d50279c53169809ae7.png)

---

_[View the full topic](https://discuss.elastic.co/t/showing-tps-on-line-visulaize/286898)._