# Scaling out percolator performance?
**URL:** https://discuss.elastic.co/t/scaling-out-percolator-performance/18755
**Category:** Elasticsearch
**Created:** [July 21, 2014, 4:57am UTC](https://discuss.elastic.co/t/scaling-out-percolator-performance/18755 "2014-07-21T04:57:56Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Seungjin\_Lee](https://discuss.elastic.co/u/Seungjin_Lee)
#### Post date: [July 21, 2014, 4:57am UTC](https://discuss.elastic.co/t/scaling-out-percolator-performance/18755/1 "2014-07-21T04:57:56Z")
Hi all,
for testing, I have one index with only 1 shard and 4 replicas.
in .percolator type of that index, there are 1.5k queries to be percolated.
and total 5 modern machines with 48G ram, assinged 12G for elasticsearch on
each node.
What I'm seeing now is, it rarely scales out in performance perspective of
view.
with only 1 node, percolate throughput is about 15k/s
with 5 nodes, it's about 18k/s.
I thought that If I have 1 shard and make number of replica same as number
of machines we have, performance statistic will also linearly scales out as
number of node increases.
any comment will be very helpful
thanks
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAL3\_U42E%3DoqH%2BXQ7svkf5FdEV2fM5DxZr5pGNFcwvTcw-h%2BzvQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAL3_U42E%3DoqH%2BXQ7svkf5FdEV2fM5DxZr5pGNFcwvTcw-h%2BzvQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@spinscale](https://discuss.elastic.co/u/spinscale)
#### Post date: [August 4, 2014, 8:02am UTC](https://discuss.elastic.co/t/scaling-out-percolator-performance/18755/2 "2014-08-04T08:02:04Z")
Hey,
there are several possibilties to increase performance. First you can have
your own index for your percolation queries, so it scales independently
from your data (there are use-cases where people do not have increasing
data, but ever increasing amount of percolators). Second you can filter
during percolation, so that a document is not executed against every
registered query in case you already know, that some are not important.
See
> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.
However, if you only have 1 shard, you should be able to scale out anyway.
Can you check your stats? Do you hit all those nodes evenly? Maybe you
created some 'hot node'?
--Alex
On Mon, Jul 21, 2014 at 6:57 AM, Seungjin Lee [sweetest0409@gmail.com](mailto:sweetest0409@gmail.com)
wrote:
> Hi all,
>
> for testing, I have one index with only 1 shard and 4 replicas.
>
> in .percolator type of that index, there are 1.5k queries to be percolated.
>
> and total 5 modern machines with 48G ram, assinged 12G for elasticsearch
> on each node.
>
> What I'm seeing now is, it rarely scales out in performance perspective of
> view.
>
> with only 1 node, percolate throughput is about 15k/s
>
> with 5 nodes, it's about 18k/s.
>
> I thought that If I have 1 shard and make number of replica same as number
> of machines we have, performance statistic will also linearly scales out as
> number of node increases.
>
> any comment will be very helpful
>
> thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit
> [https://groups.google.com/d/msgid/elasticsearch/CAL3\_U42E%3DoqH%2BXQ7svkf5FdEV2fM5DxZr5pGNFcwvTcw-h%2BzvQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAL3_U42E%3DoqH%2BXQ7svkf5FdEV2fM5DxZr5pGNFcwvTcw-h%2BzvQ%40mail.gmail.com)
> [https://groups.google.com/d/msgid/elasticsearch/CAL3\_U42E%3DoqH%2BXQ7svkf5FdEV2fM5DxZr5pGNFcwvTcw-h%2BzvQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAL3_U42E%3DoqH%2BXQ7svkf5FdEV2fM5DxZr5pGNFcwvTcw-h%2BzvQ%40mail.gmail.com?utm_medium=email&utm_source=footer)
> .
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9ZVdfcZdVUK%2Bg53bLL1GyAMGwAFerOHWqitkZRKKLmPQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGCwEM9ZVdfcZdVUK%2Bg53bLL1GyAMGwAFerOHWqitkZRKKLmPQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:11am UTC](https://discuss.elastic.co/t/scaling-out-percolator-performance/18755/3 "2017-07-06T01:11:13Z")