I think there are two potential causes: - refreshes - id lookups Refreshes run periodically in order to make data fast to search, http://www.elasticsearch.org/blog/performance-considerations-elasticsearch-indexing/ gives recommandations to improve indexing speed by increasing the refresh interval.
Id lookups are required in order to check if the document that you are indexing is replacing another document. Note however that since Elasticsearch 1.2, Elasticsearch can skip this step if you use auto-generated ids: https://github.com/elasticsearch/elasticsearch/pull/5917 On Wed, Nov 5, 2014 at 9:14 AM, 이윤동 <[email protected]> wrote: > hi! my first question! > > if replica 0 bulk index, then disk read, write ratio same. > but batch finish after... disk read is high than write. > disk read = 10 X disk write... > > so cpu load is high, then batch index very slow.. T.T > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/8b0c64a1-6aec-4e3c-a13a-723087919c77%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/8b0c64a1-6aec-4e3c-a13a-723087919c77%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Adrien Grand -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6GROAzcX0BChLjfcgKP7TaKt-sBoTukrpc2a4W2U0%2BuA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
