# A question for result benchmark
**URL:** https://discuss.elastic.co/t/a-question-for-result-benchmark/76587
**Category:** Elasticsearch
**Tags:** rally
**Created:** [February 27, 2017, 8:17am UTC](https://discuss.elastic.co/t/a-question-for-result-benchmark/76587 "2017-02-27T08:17:31Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@phucvinh52](https://discuss.elastic.co/u/phucvinh52)
#### Post date: [February 27, 2017, 8:17am UTC](https://discuss.elastic.co/t/a-question-for-result-benchmark/76587/1 "2017-02-27T08:17:31Z")
I have a result benchmark
> **[benchmark elasticsearch](https://docs.google.com/spreadsheets/d/1DtZw7omQR5jqehCCtgJn-tY2H0Nnepktt6cJ4mgGzZM/edit?usp=sharing)**
>
> Sheet1
>
> | Lap | Metric | Operation | Value | Unit |(1 master 3 data 0 replicas),| Lap | Metric | Operation | Value | Unit |(1 master 2data) 1 replicas,| Lap | Metric | Operation | Value | Unit |1 master 3 data 1...
When I increase data node and replicas, term latency increase and throught put decrease. Do my config have a problem?
This is my config es master so same es data
> ```
> cluster.name: cluster-es
> node.name: node-xxx
> network.host: ["xxx.90.33.22"]
> http.port: 9200
> discovery.zen.ping.unicast.hosts: ["xxx.90.33.18"]
> discovery.zen.minimum_master_nodes: 2
> thread_pool.search.queue_size: 1000000
> thread_pool.bulk.queue_size: 1000000
> indices.breaker.fielddata.limit: 75%
>
> ```
---
### Author:  [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [February 27, 2017, 9:02am UTC](https://discuss.elastic.co/t/a-question-for-result-benchmark/76587/2 "2017-02-27T09:02:29Z")
Hi @phucvinh52,
I don't know anything about your benchmark setup (e.g. how did you invoke Rally? On which hardware did you run Rally? How was Rally connected to your cluster?) but there are a lot of throughput numbers missing in the first case (3 data nodes, no replicas). This is an indication for error responses (unfortunately, we don't [show the error rate in the summary report](https://github.com/elastic/rally/issues/234) yet which would make it very obvious) .
- Did you check the log files of Elasticsearch and Rally for any errors?
- Did you specify _all_ your data nodes in the `--target-hosts` parameter?
Also: These huge queue sizes do more harm than good. You should reduce them significantly (just use the default values). If your queues are constantly full this means that you are throwing more load at the system than it can handle and you should rather increase your capacity (e.g. more nodes, more RAM, more CPU - depends on what you're bottlenecked) than increasing the queue size as the latter just hides the actual problems.
Daniel
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 27, 2017, 9:02am UTC](https://discuss.elastic.co/t/a-question-for-result-benchmark/76587/3 "2017-03-27T09:02:30Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.