I would add that if you only have a single port, you can now add multi-tunneling (number of tunnels per route), to increase performance.  This is available in network topologies in Command Center and in outgoing routes tab in Java.

Alireza B wrote:
Please note with CVD port in additional data ports, Client will transfer the data directly to MA on CVD port bypassing the firewall tunnel and it’s protocol.

Do note that this ‘protocol’ here will be unecrypted.

While opening port 8400 may/will increase stream performance, for highly secured environments or if encrypted during transit is a requirement this may lead to unwanted situations!

Furthermore with the “Number of tunnels per route” option nowadays the performance gain of opening port 8400 is not that much in my personal experience.

As such I nowadays would not recommend adding port 8400 there.

my 0.02

​

Agreed and will also bypass throttling if you have set any in place - the feature @MFasulo mentioned is a much better way to improve performance than the CVD port trick, but the old method is still there too with the aforementioned caveats.

The method I provided leaves the protocol intact, but improves performance by segmenting control/data traffic, which reduces latency/increases efficiency.   In testing “4” seems to be the magic number

Agree on the multi tunneling feature and in our tests we could see the most benefit will be seen in proxy-based scenarios rather than direct connections. In a production environment(Clients->Proxy->MA) increasing the tunnels to 4 increased the performance just more than 3 times! 

Just to clarify, I dont believe we can do throttling & Multi-Tunnels at the same time 

Documentation recommends NOT to configure throttling when increasing number of tunnels.