Thanks! This makes a lot of sense and it is pretty reaffirming to know that
data won't be lost without an error.
I'm guessing your right about the jagged index rate, as the graph is pretty
consistent across different levels of load. I'll definitely be looking into
bulk as load grows.
Cheers,
"10 index a second" is not too much.
Note, the jagged rate may also result from a skew in the measurement
intervals, so it may be artificial and no need to worry too much.
Bulk is definitely the way to go. With bulk mode, you can index around
10k-20k docs per second (avg size of 1k) from a single
I'm using ES 1.3 to ingest information from multiple ( 25 ) servers. Our
servers are indexing a single document at a time using the Java API,
totally about 100-200 documents per second depending on the time. In
Marvel, I see the index requests as a very jagged graph
(
https://www.dropbox.com/
