# Nodes Stats API - not only how much but also how fast?

**URL:** <https://discuss.elastic.co/t/nodes-stats-api-not-only-how-much-but-also-how-fast/7059>\
**Category:** Elasticsearch\
**Created:** [March 19, 2012, 4:03pm UTC](https://discuss.elastic.co/t/nodes-stats-api-not-only-how-much-but-also-how-fast/7059 "2012-03-19T16:03:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [March 19, 2012, 4:03pm UTC](https://discuss.elastic.co/t/nodes-stats-api-not-only-how-much-but-also-how-fast/7059/1 "2012-03-19T16:03:10Z")

</div>

Hi,

the Nodes Stats API in 0.19.x contains a lot of useful info, but I am still  
missing something. If I read it correctly it can tell us how much of the  
data has gone through transport layer (node / transport) and how much data  
has been read or written to the disk (node / fs / data) but it does not  
tell me how fast it has been able to do it.

In other words, I would love to see ES to be able to tell if underlying  
network and general IO interface is fast enough to support fast search  
responses. Is that possible?

Regards,  
Lukas

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [March 20, 2012, 9:52am UTC](https://discuss.elastic.co/t/nodes-stats-api-not-only-how-much-but-also-how-fast/7059/2 "2012-03-20T09:52:45Z")

</div>

How "fast" is basically the delta (simplest) or more complex computation  
between one sample and the next. Its certainly something that can be  
computed in ES as well, but stats is focused on providing the "raw" data  
currently.

On Mon, Mar 19, 2012 at 6:03 PM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:

> Hi,
> 
> the Nodes Stats API in 0.19.x contains a lot of useful info, but I am  
> still missing something. If I read it correctly it can tell us how much of  
> the data has gone through transport layer (node / transport) and how much  
> data has been read or written to the disk (node / fs / data) but it does  
> not tell me how fast it has been able to do it.
> 
> In other words, I would love to see ES to be able to tell if underlying  
> network and general IO interface is fast enough to support fast search  
> responses. Is that possible?
> 
> Regards,  
> Lukas

---

<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 6, 2017, 3:35am UTC](https://discuss.elastic.co/t/nodes-stats-api-not-only-how-much-but-also-how-fast/7059/3 "2017-07-06T03:35:30Z")

</div>

Closed on July 6, 2017, 3:35am UTC