I am encountering a performance issue with Elasticsearch in Amazon EC2.
Currently I am getting at most 500 rps using ab - Apache HTTP server
benchmarking tool with a very simple query. Our goal is to get to atleast
1000 rps, but it seems unlikely unless we throw more hardware at it. Any
advice would be greatly appreciated.
Configurations:
8 node cluster - m1.xlarge - 4 are EBS optimized
Default memory(5gbs)
Java version 1.7.0_03
OS Ubuntu 12.04.1
active shards 4
replicas 1
number of documents: 1.5millions
each document has about 400 attributes that are searchable, they are of
varying data types.
here are the analyzers that are applied to all string fields:
I am encountering a performance issue with Elasticsearch in Amazon EC2.
Currently I am getting at most 500 rps using ab - Apache HTTP server
benchmarking tool with a very simple query. Our goal is to get to atleast
1000 rps, but it seems unlikely unless we throw more hardware at it. Any
advice would be greatly appreciated.
Configurations:
8 node cluster - m1.xlarge - 4 are EBS optimized
Default memory(5gbs)
Java version 1.7.0_03
OS Ubuntu 12.04.1
active shards 4
replicas 1
number of documents: 1.5millions
each document has about 400 attributes that are searchable, they are of
varying data types.
here are the analyzers that are applied to all string fields:
On Mon, Dec 17, 2012 at 2:20 PM, Jason Moore <jason....@gmail.com<javascript:>
wrote:
I am encountering a performance issue with Elasticsearch in Amazon EC2.
Currently I am getting at most 500 rps using ab - Apache HTTP server
benchmarking tool with a very simple query. Our goal is to get to atleast
1000 rps, but it seems unlikely unless we throw more hardware at it. Any
advice would be greatly appreciated.
Configurations:
8 node cluster - m1.xlarge - 4 are EBS optimized
Default memory(5gbs)
Java version 1.7.0_03
OS Ubuntu 12.04.1
active shards 4
replicas 1
number of documents: 1.5millions
each document has about 400 attributes that are searchable, they are of
varying data types.
here are the analyzers that are applied to all string fields:
Yes, well, as you speculate you may simply end up needing more memory. But
first here is a list of "levers". Try them one by one and see which of them
work for you:
mlockall : true
restrict the number of docs returned to 5 or even 1 if possible
mmapFS
up replicas from 4/1 to 4/2, even 4/3. This allows each query to be
answered by fewer nodes and (if your nodes have spare capacity) it will
increase throughput
Use bigdesk to understand what your current constraint (memory/cpu/disk io)
is likely to be. Make sure that all nodes are at roughly the same cpu
utilization, i.e. that the query workload is balanced across your cluster.
I am encountering a performance issue with Elasticsearch in Amazon EC2.
Currently I am getting at most 500 rps using ab - Apache HTTP server
benchmarking tool with a very simple query. Our goal is to get to atleast
1000 rps, but it seems unlikely unless we throw more hardware at it. Any
advice would be greatly appreciated.
Configurations:
8 node cluster - m1.xlarge - 4 are EBS optimized
Default memory(5gbs)
Java version 1.7.0_03
OS Ubuntu 12.04.1
active shards 4
replicas 1
number of documents: 1.5millions
each document has about 400 attributes that are searchable, they are of
varying data types.
here are the analyzers that are applied to all string fields:
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.