# How to estimate the max query throughput
**URL:** https://discuss.elastic.co/t/how-to-estimate-the-max-query-throughput/155475
**Category:** Elasticsearch
**Created:** [November 6, 2018, 4:14am UTC](https://discuss.elastic.co/t/how-to-estimate-the-max-query-throughput/155475 "2018-11-06T04:14:30Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Jianzhou\_Z](https://discuss.elastic.co/u/Jianzhou_Z)
#### Post date: [November 6, 2018, 4:14am UTC](https://discuss.elastic.co/t/how-to-estimate-the-max-query-throughput/155475/1 "2018-11-06T04:14:30Z")
My query QPS is less than 100, and was wondering what is the max possible throughput for the query.
The index has 16 shards (1 primary + 1 replica). The cluster has 11 nodes. Each node has 32 CPUs, 70G memory, 900G SSD drive. One query takes 5-10ms if I run it via kibana. If we run query sequentially, QPS is like 100.
Profiler shows that each query goes through 16 shards, so each node may need to query 2 shards.
Each node has 32 CPUs. The default search thread pool size is 3/2 \* 32 = 48. So 48/2 = 24 such a query can run in parallel on a node. So the QPS with parallel query could be 4,800.
I can image given concurrency overhead or maybe some part of a query cannot be parallel. So the real QPS must be smaller than 4800.
However my QPS is 100. It is like there is no parallel at all... Is this expected?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 4, 2018, 4:14am UTC](https://discuss.elastic.co/t/how-to-estimate-the-max-query-throughput/155475/2 "2018-12-04T04:14:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.