Member Avatar for thiyagu1981

We have SAP and Java application hosted in remote server. The users are connecting to the other side of the world, through a VPN tunnel to the remote server; RDPing into a terminal services server and then running SAP and Java.
The users are reporting slowness in accessing the applications and latency is 156 ms average
where we can optimize things, Is this a problem of SAP&Java application with RDP, or what. Can anyone offer any ideas on things to try?
The users are comparing our app with another division's app, saying the other one performs better. Both basically do the same thing.
How does the application architecture affect things? Is there anything I can look into to see if I can improve things?

Thanks!

  • 2 Contributors
  • 2 Replies
  • 290 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by thiyagu1981

Dani AI

Generated

Short take for (and thanks to for the routing question): interactive RDP is extremely sensitive to round‑trip time (RTT), jitter and packet loss — not just raw bandwidth. Changing tunnel software (IPsec → SSH) rarely fixes a high RTT unless it gives you a different network route or avoids packet fragmentation; the first step is to measure and prove where the delay or loss happens. (cloudflare.com)

Immediate, practical tests to run (capture before/after any change):

# from a client
ping -n 50 <terminal-server-ip>
tracert -d <terminal-server-ip>
pathping -n <terminal-server-ip>

# from a test host on each VPN endpoint
# start server on one side
iperf3 -s
# run client test from the other side
iperf3 -c <test-host-ip> -P 4 -t 30

Also run WinMTR from affected clients and collect several 1–2 minute traces at peak time. These show per‑hop loss/jitter and help identify ISP or tunnel problems. (learn.microsoft.com)

Tuning suggestions (what actually moves the needle)

  • Enable RDP shortpath/UDP (RDP 8+/RemoteFX features) and ensure UDP 3389 is allowed through firewalls/VPNs — UDP reduces retries that kill interactive feel. (support.microsoft.com)
  • Check MTU/MSS and avoid fragmentation inside the tunnel (encapsulation adds bytes; PMTU issues cause retransmits and latency). If the tunnel reduces effective MTU, clamp MSS on TCP flows or increase MTU end‑to‑end. (arista.com)
  • Verify terminal server CPU, disk and app architecture (chatty SAP/Java calls will amplify RTT). Consider RemoteApp/Session placement closer to users or WAN acceleration/SD‑WAN if path cannot be shortened.

Suggested priority: (1) collect WinMTR + pathping + iperf results, (2) compare routes for both divisions, (3) check MTU/fragmentation and terminal‑server load, (4) enable RDP UDP/shortpath in a pilot, (5) consider WAN/peering changes or relocating app tiers.

Recommended Answers

All 2 Replies

Member Avatar for freshfitz

Is the other divisions app on the same server, How is the vpn setup is it hardware to hardware or windows dial up?

Member Avatar for thiyagu1981

Other divsion is using the application hosted in the different server through different VPN tunnel.
It is hardware to hadware VPN configured through IPSec tunnels.
Does Replacing of IPSec tunnels by SSH tunnels will work out to resolve the issue.
Hope this will feed your thoughts to resolve the issue.
What are the possible options to reduce the latency from 153ms

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.