# Elasticsearch performance decrement after new index creation **URL:** \ **Category:** Elasticsearch\ **Created:** [July 1, 2013, 9:52am UTC](https://discuss.elastic.co/t/elasticsearch-performance-decrement-after-new-index-creation/12595 "2013-07-01T09:52:13Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Vahid](https://avatars.discourse-cdn.com/v4/letter/v/96bed5/32.png) [@Vahid](https://discuss.elastic.co/u/Vahid)\ **Post date:** [July 1, 2013, 9:52am UTC](https://discuss.elastic.co/t/elasticsearch-performance-decrement-after-new-index-creation/12595/1 "2013-07-01T09:52:13Z")
Hi all, We have a 16 nodes cluster with some indexes (let say 9 active indexes and 10 empty and not used indexes) with 51 primary shards and 1 replica. At startup we had 3 active indexes, reading from one and indexing into next two. Search speed and indexing were satisfying for us. I've created 6 new indexes and started searching and indexing on them. Performance about 4 time decreased, even destination indexes are almost empty and it must be faster at indexing startup. The strange thing is that some nodes have high cpu usage(near 20-30 %) because of ES threads when there is no indexing and searching request. I read some threads in the forum regarding ES high cpu usage and set the network.tcp.blocking to true, but didn't improve. The only thing I've changed is that previously 100,000 filter criteria(using or bool filters) were set to the search query and now its 1 million, however the loading and indexing documents are same as before. ES configuration: bootstrap.mlockall: true discovery.zen.fd.ping\_interval: 10 http.port: 9200 network.publish\_host: ....147 index.cache.filter.max\_size: 10 discovery.zen.minimum\_master\_nodes: 9 discovery.zen.fd.ping\_timeout: 60s index.cache.field.expire: 1m gateway.recovery\_after\_nodes: 15 gateway.expected\_nodes: 16 discovery.zen.fd.ping\_retries: 10 index.cache.filter.expire: 1m index.number\_of\_replicas: 1 transport.tcp.compress: true discovery.zen.ping.unicast.hosts: ["cluster ips"] network.tcp.blocking: true gateway.recovery\_after\_time: 5m index.number\_of\_shards: 51 indices.cache.filter.size: 64mb discovery.zen.ping.timeout: 60s index.query.bool.max\_clause\_count: 65536 node.name: .... discovery.zen.ping.multicast.enabled: false action.auto\_create\_index: false index.cache.field.type: resident index.refresh\_interval: -1 Thanks for any help, Vahid -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Vahid](https://avatars.discourse-cdn.com/v4/letter/v/96bed5/32.png) [@Vahid](https://discuss.elastic.co/u/Vahid)\ **Post date:** [July 1, 2013, 11:49am UTC](https://discuss.elastic.co/t/elasticsearch-performance-decrement-after-new-index-creation/12595/2 "2013-07-01T11:49:51Z")
These are also additional info may help. Using elasticsearch-0.20.5. Profiled ES process and the following thread uses most of the cpu usage while ES is idle: org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run() org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run() org.elasticsearch.common.netty.channel.socket.oio.OioWorker.run() org.elasticsearch.common.netty.channel.socket.oio.AbstractOioWorker.run() org.elasticsearch.common.netty.channel.socket.oio.OioWorker.process() java.io.PushbackInputStream.read() . -- 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). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:28am UTC](https://discuss.elastic.co/t/elasticsearch-performance-decrement-after-new-index-creation/12595/3 "2017-07-06T02:28:48Z")