# Need Details on ops/sec

**URL:** <https://discuss.elastic.co/t/need-details-on-ops-sec/180729>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [May 13, 2019, 4:41am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729 "2019-05-13T04:41:16Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Balmukund](https://avatars.discourse-cdn.com/v4/letter/b/e5b9ba/32.png) [@Balmukund](https://discuss.elastic.co/u/Balmukund)\
**Post date:** [May 13, 2019, 4:41am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/1 "2019-05-13T04:41:16Z")

</div>

Hi,  
I am using Search query which gives the result as below.

All,Min Throughput,relative-kibana-discover\_50%,0.02,ops/s  
All,Median Throughput,relative-kibana-discover\_50%,0.02,ops/s  
All,Max Throughput,relative-kibana-discover\_50%,0.08,ops/s

So, just wanted to understand the meaning of ops/s here.

--Regards,  
Balmukund

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 13, 2019, 5:52am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/2 "2019-05-13T05:52:38Z")

</div>

That is the number of operations of that type run per second. These are reasonably heavy queries scheduled to run at regular intervals, which explains the low number of ops/sec.

---

<div class="post-metadata">

**Author:** ![Balmukund](https://avatars.discourse-cdn.com/v4/letter/b/e5b9ba/32.png) [@Balmukund](https://discuss.elastic.co/u/Balmukund)\
**Post date:** [May 13, 2019, 8:37am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/3 "2019-05-13T08:37:13Z")

</div>

Hi Christian,  
Thank you for your prompt response. It would be great if you could highlight the operations in the below custom query.

{  
"name": "custom\_query",  
"operation-type": "search",  
"index": "elasticlogs\_\*",  
"body": {  
"query": {"bool":  
{"must": [{"bool": {"should": [  
{"match": {"nginx.access.geoip.country\_name": ""}},  
{"match": {"nginx.access.geoip.country\_iso\_code": ""}}  
]}},  
{"bool": {"should": [  
{"match": {"nginx.access.user\_agent.os\_name": "Mac OS X"}},  
{"match": {"nginx.access.user\_agent.device": "Other"}}  
]}},  
{"bool": {"should": [  
{"match": {"nginx.access.geoip.continent\_name": "Asia"}},  
{"match": {"nginx.access.response\_code": "200"}}  
]}},  
{"bool": {"should": [{"match": {"nginx.access.geoip.city\_name": ""}},  
{"match": {"nginx.access.remote\_ip": "203.112.82.0"}}  
]}}  
]}}  
}  
}  
Basically, I want to understand, is it the number of operations of a query per sec?

--Regards,  
Balmukund

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 13, 2019, 8:49am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/4 "2019-05-13T08:49:25Z")

</div>

I am not sure I understand. If you have a look at the track is structured you will see how it is configured.

---

<div class="post-metadata">

**Author:** ![Balmukund](https://avatars.discourse-cdn.com/v4/letter/b/e5b9ba/32.png) [@Balmukund](https://discuss.elastic.co/u/Balmukund)\
**Post date:** [May 13, 2019, 9:11am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/5 "2019-05-13T09:11:41Z")

</div>

Hi Christian,  
Thank you for your reply.  
How do you define operations in the above query? Also, ops/sec means query per sec here?

Please find below operation type.

"schedule": [  
{  
"operation": "delete-index"  
},  
{  
"operation": {  
"operation-type": "create-index",  
"settings": {  
"index.number\_of\_replicas": {{ number\_of\_replicas | default(0) }},  
"index.number\_of\_shards": {{ shard\_count | default(2) }}  
}  
}  
},  
{  
"operation": "index-append-1000",  
"warmup-time-period": 0,  
"time-period": 1200,  
"clients": {{ p\_bulk\_indexing\_clients }}  
}  
]

Please elaborate here, ops/sec.

--Regards,  
Balmukund

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 13, 2019, 9:29am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/6 "2019-05-13T09:29:00Z")

</div>

The first two operations there runs only once, which means ops/sec does not really mean much. The last one is not rate limited (unlike the queries you mentioned earlier) so that ops/sec will vary. Please have a look at the esrally documentation as this describes the structure of a track and the configuration options.

---

<div class="post-metadata">

**Author:** ![Balmukund](https://avatars.discourse-cdn.com/v4/letter/b/e5b9ba/32.png) [@Balmukund](https://discuss.elastic.co/u/Balmukund)\
**Post date:** [May 13, 2019, 10:04am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/7 "2019-05-13T10:04:18Z")

</div>

Hi Christian,  
Thank you for your reply. I went through various documents and tried to understand but still have little doubts.I think, below example can make me clear. Sorry, to ask it again and again.

{  
"schedule": [  
{  
"operation": {  
"operation-type": "search",  
"index": "\_all",  
"body": {  
"query": {  
"match\_all": {}  
}  
}  
},  
"warmup-iterations": 100,  
"iterations": 100,  
"target-throughput": 10  
}  
]  
}  
So, here " **search**" type operation runs 100 times. It calculates per sec operations from this iterations. Please correct me my understanding.

--Regards,  
Balmukund

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 13, 2019, 11:42am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/8 "2019-05-13T11:42:34Z")

</div>

Here the target throughput is 10 ops/sec which is what esrally will try to achieve. It will not go higher than this.

---

<div class="post-metadata">

**Author:** ![Balmukund](https://avatars.discourse-cdn.com/v4/letter/b/e5b9ba/32.png) [@Balmukund](https://discuss.elastic.co/u/Balmukund)\
**Post date:** [May 13, 2019, 2:59pm UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/9 "2019-05-13T14:59:12Z")

</div>

Hi Christian,  
Thank you very much for your explanation.

--Regards,  
Balmukund

---

<div class="post-metadata">

**Author:** ![Balmukund](https://avatars.discourse-cdn.com/v4/letter/b/e5b9ba/32.png) [@Balmukund](https://discuss.elastic.co/u/Balmukund)\
**Post date:** [May 14, 2019, 9:11am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/10 "2019-05-14T09:11:59Z")

</div>

Hi Christian,  
How to check the number of merge threads in elasticsearch?

--Regards,  
Balmukund

---

<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:** [June 11, 2019, 9:12am UTC](https://discuss.elastic.co/t/need-details-on-ops-sec/180729/11 "2019-06-11T09:12:00Z")

</div>

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