# Node stats - indices.search.scroll\_time\_in\_millis **URL:** \ **Category:** Elasticsearch\ **Created:** [April 6, 2020, 9:21am UTC](https://discuss.elastic.co/t/node-stats-indices-search-scroll-time-in-millis/226660 "2020-04-06T09:21:21Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![whatgeorgemade](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/whatgeorgemade/32/103246_2.png) [@whatgeorgemade](https://discuss.elastic.co/u/whatgeorgemade)\ **Post date:** [April 6, 2020, 9:21am UTC](https://discuss.elastic.co/t/node-stats-indices-search-scroll-time-in-millis/226660/1 "2020-04-06T09:21:21Z")
I've been looking through some stats in a customer's cluster and have noticed a lot of time is being spent performing scroll operations, according to `indices.search.scroll_time_in_millis`. There is a legitimate use-case for this but I'm not sure what time actually gets reported so I'm not certain if the large amount of time spent doing them is really an issue. I thought it could be the time spent doing the associated fetches but there's already `indices.search.fetch_time_in_millis`. Is scroll fetch split out? Does the scroll timeout play a part in how the number is reported? Am I right in thinking the number never gets reset and will cover the lifetime of the index? Is there a reference I can see to give some more in-depth information on how all the stats in the API are calculated? Thanks in advance, George. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 4, 2020, 9:21am UTC](https://discuss.elastic.co/t/node-stats-indices-search-scroll-time-in-millis/226660/2 "2020-05-04T09:21:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.