# Performance problem with indexing on a single node **URL:** \ **Category:** Elasticsearch\ **Created:** [September 12, 2012, 11:29am UTC](https://discuss.elastic.co/t/performance-problem-with-indexing-on-a-single-node/9001 "2012-09-12T11:29:49Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Vahid](https://avatars.discourse-cdn.com/v4/letter/v/96bed5/32.png) [@Vahid](https://discuss.elastic.co/u/Vahid)\ **Post date:** [September 12, 2012, 11:29am UTC](https://discuss.elastic.co/t/performance-problem-with-indexing-on-a-single-node/9001/1 "2012-09-12T11:29:49Z")
Hi, We have faced some performance problems with just a single ES node. At first when there is no data in the index the index speed is about 31Mb/s after increasing the size of indexed data it goes to 15~20Mb/s. we are using the elasticsearch-0.19.8 for storing and indexing our big data. this is ES java options : -Xms16g -Xmx16g -Xss256k bootstrap.mlockall: true 5 primary shards without any replica 32g ram, 8 core, 2.2T free disk space on local machine, just one node on one machine, so there is no clustering and so on... H.D.D write speed ~ 142Mb/s we are using bulk add to add 10000 doc at once, the size ~ 625 Mb one of the fields which contains almost hole the data for each record is not supposed to index, so is set to not analyzed and not indexed. by this it could be like writing data on disk not indexing As you see there is no clustering, allocated memory is enough and there is enough space on the disk. Thank you very much. -- ---
**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, 3:13am UTC](https://discuss.elastic.co/t/performance-problem-with-indexing-on-a-single-node/9001/2 "2017-07-06T03:13:02Z")