review:
Bulk syntax requires: Each string can not wrap json, json different strings must wrap
Why not use standard json array it? Such as:
[
{
"create":{...}
},
{
"update":{...}s
}
]
Because, if this Json array, ES need to do is
-
Json string converted into an array of objects
-
Designated by the index Json each, type, id, routed to the corresponding shard
-
Performing operations on the corresponding shard
You can see, first of all,
string Json turn is time-consuming
; secondly, ES need to save a string in memory, a Json object is duplicate data. Thus, when a large bulk content when ES will lead to unnecessary memory footprint, but will affect the search, aggregation request rate, and
a lot of junk data, will cause the jvm GC more, take up more time
.
And, if the bulk of the provisions, each with a row of json way,
ES need to do is:
-
Segmentation request string
-
Take the command type (create, update), index, type
-
Each line string directly (or every two rows), made up to the corresponding shard, get away.
There will be no memory wasted time and unnecessary expenses.
So, this syntax, the main consideration is the ES performance issues. Worth learning