I am facing the same issue . When I use curl to get response , it takes around 40-50 ms . But When same query is executed using execute().actionGet() using TransportClient , it takes around 1000 ms. Trying to figure out the root cause and the solution of this problem . Settings settings = Settings.…

Java Transport Client slower than curl request

dadoonet (David Pilato) October 3, 2016, 5:26pm 3

Can you describe what you have in orFilterCatId, perPage?
May be print with a srb.toString() what does the request looks like?

Also can you give the exact query you are running with curl?

Topic		Replies	Views
Elasticsearch Java client much slower than rest call Elasticsearch	7	4331	July 5, 2017
Elasticsearch 1.1.0 Java API Slower Than Curl for Certain Queries Elasticsearch	10	589	July 6, 2017
Java Client slower than http Elasticsearch	9	3281	July 6, 2017
Native Java API is slower than the REST one Elasticsearch	3	1505	July 5, 2017
Elasticsearch Transport client performance vs. Sense plugin Elasticsearch	7	1393	July 5, 2017