# Transport client / Two hop **URL:** \ **Category:** Elasticsearch\ **Created:** [May 29, 2013, 8:24am UTC](https://discuss.elastic.co/t/transport-client-two-hop/12166 "2013-05-29T08:24:50Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Nicolas\_Labrot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolas_labrot/32/2177_2.png) [@Nicolas\_Labrot](https://discuss.elastic.co/u/Nicolas_Labrot)\ **Post date:** [May 29, 2013, 8:24am UTC](https://discuss.elastic.co/t/transport-client-two-hop/12166/1 "2013-05-29T08:24:50Z")
Hi, I test two configurations: 1. C1: An index with 1 primary shard and 0 replica shard. Primary shard is on one server. The transport client is configured with the ES instance. 2. C2: An index with 1 primary shard and 1 replica shard. Primary shard is on one server and replica on another. The transport client is configured with the 2 ES instances. Network is monitored during a search load: 1. C1 : Reception ≈ 5Mb/s | Transmission ≈ 180Mb/s 2. C2 : For each server : Reception ≈ 50Mb/s | Transmission ≈ 180Mb/s I'm wondering why such a difference between C1 and C2 reception? Is what the "two hop" means? Does it can explain that I get only a 25% request/s boost between C1 and C2? Is the node client can improve this? Thanks for your help! Nicolas -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Nicolas\_Labrot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nicolas_labrot/32/2177_2.png) [@Nicolas\_Labrot](https://discuss.elastic.co/u/Nicolas_Labrot)\ **Post date:** [June 3, 2013, 7:37am UTC](https://discuss.elastic.co/t/transport-client-two-hop/12166/2 "2013-06-03T07:37:54Z")
Here is a gatling results of the C2 configuration : At 13:02:50 I stop the replica shard. There is small difference of the number of query/s. At 13:03:25 I restart the replica shard. Le mercredi 29 mai 2013 10:24:50 UTC+2, Nicolas Labrot a écrit : > Hi, > > I test two configurations: > > 1. C1: An index with 1 primary shard and 0 replica shard. Primary > shard is on one server. The transport client is configured with the ES > instance. > 2. C2: An index with 1 primary shard and 1 replica shard. Primary > shard is on one server and replica on another. The transport client is > configured with the 2 ES instances. > > Network is monitored during a search load: > > 1. C1 : Reception ≈ 5Mb/s | Transmission ≈ 180Mb/s > 2. C2 : For each server : Reception ≈ 50Mb/s | Transmission ≈ 180Mb/s > > I'm wondering why such a difference between C1 and C2 reception? Is what > the "two hop" means? Does it can explain that I get only a 25% request/s > boost between C1 and C2? Is the node client can improve this? > > Thanks for your help! > > Nicolas -- 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 [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:33am UTC](https://discuss.elastic.co/t/transport-client-two-hop/12166/3 "2017-07-06T02:33:23Z")
Closed on July 6, 2017, 2:33am UTC