I have been running some performance tests with some bulk indexing requests. One thing that is puzzling me is that I see pretty similar latency/cluster CPU usage when using the node vs transport client (client is on same network, cluster of 4 nodes). I am not that familiar with the client code, but as far as I can tell, the bulk request tries to divide up the documents per shard and route them using multiple requests. I would think this would lower cluster CPU usage and latency as the documents would be sent to the right node immediately rather than a potential 2 hop operation when using the transport client? My reasoning is that on the initial client -> node request, may need to parse the request and then re-route the portion of requests that need to go to another node. Those re-routed requests would then need to be re-parsed.
-- 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/f1e1448a-76d3-4e9d-bb3e-a5dff827e241%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
