# "Took" Field value in the Search Response

**URL:** <https://discuss.elastic.co/t/took-field-value-in-the-search-response/110722>\
**Category:** Elasticsearch\
**Created:** [December 7, 2017, 5:30pm UTC](https://discuss.elastic.co/t/took-field-value-in-the-search-response/110722 "2017-12-07T17:30:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zhengcong\_Yin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhengcong_yin/32/62960_2.png) [@Zhengcong\_Yin](https://discuss.elastic.co/u/Zhengcong_Yin)\
**Post date:** [December 7, 2017, 5:30pm UTC](https://discuss.elastic.co/t/took-field-value-in-the-search-response/110722/1 "2017-12-07T17:30:36Z")

</div>

I read previous posts regarding what does "took" measure. Does it including the time to distribute the query and merger the result?

I run some geo-point search benchmarks for a cluster(3master, 4 data nodes, 1 client, 4cores 16G RAM VMs). The cluster with replica shards seems like show better scalability than the cluster without shards (just allocate the primary shards to 1/2/3/4 nodes) in terms of average "took" value. Is that reasonable?

Thanks,

---

<div class="post-metadata">

**Author:** ![s1monw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s1monw/32/3637_2.png) [@s1monw](https://discuss.elastic.co/u/s1monw)\
**Post date:** [December 15, 2017, 10:33am UTC](https://discuss.elastic.co/t/took-field-value-in-the-search-response/110722/2 "2017-12-15T10:33:49Z")

</div>

if you have replicas you might distribute your search requests across different machines, so yes it might scale better. The took time includes distribution of requests and merging of results.

---

<div class="post-metadata">

**Author:** ![Zhengcong\_Yin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhengcong_yin/32/62960_2.png) [@Zhengcong\_Yin](https://discuss.elastic.co/u/Zhengcong_Yin)\
**Post date:** [December 15, 2017, 4:43pm UTC](https://discuss.elastic.co/t/took-field-value-in-the-search-response/110722/3 "2017-12-15T16:43:49Z")

</div>

Hi there,

Thanks for your reply. I checked the default behavior of "Sort by distance" function and the geo-point range function. To my understanding, these queries are hard to get benefits from the additional data node, am I right?

Could you tell me what kind of metrics or measurement needs to be conducted in order to see the horizontal scalability?

---

<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:** [January 12, 2018, 4:43pm UTC](https://discuss.elastic.co/t/took-field-value-in-the-search-response/110722/4 "2018-01-12T16:43:53Z")

</div>

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