There is a correlation between higher network latency (which translates into increased delay when spawning the main window) and successful embeds.
Testing environment is a fresh and updated Windows 7 Pro (x64) VM running inside VMWare Workstation 10 with only RDM v.10.0.4.0 and Winbox v.3.0 installed. To introduce latency, I used a live linux distro called WANem to act as a gateway for the test VM. That is in turn connected to a Mikrotik RB450G running routerOS 6.18.
Before introducing latency, the Windows 7 VM gets <1ms to 1ms when pinging the Mikrotik router. The RDM embed succeeds 100% of the time in this configuration. It also has a 100% success rate when up to 10ms of network latency is introduced.
At greater than 10ms network latency, things become unstable. 11ms-39ms of latency results in embed failures, though sometimes it succeeds (I attribute the success/failure inconsistency in this range to other factors that can introduce latency into the process, such as disk access, CPU usage, etc.).
At greater than 40ms of network latency, the embed fails 100% of the time. The tab is created, but the main Winbox window is never brought inside.
edited by bstaggs on 10/20/2014
Testing environment is a fresh and updated Windows 7 Pro (x64) VM running inside VMWare Workstation 10 with only RDM v.10.0.4.0 and Winbox v.3.0 installed. To introduce latency, I used a live linux distro called WANem to act as a gateway for the test VM. That is in turn connected to a Mikrotik RB450G running routerOS 6.18.
Before introducing latency, the Windows 7 VM gets <1ms to 1ms when pinging the Mikrotik router. The RDM embed succeeds 100% of the time in this configuration. It also has a 100% success rate when up to 10ms of network latency is introduced.
At greater than 10ms network latency, things become unstable. 11ms-39ms of latency results in embed failures, though sometimes it succeeds (I attribute the success/failure inconsistency in this range to other factors that can introduce latency into the process, such as disk access, CPU usage, etc.).
At greater than 40ms of network latency, the embed fails 100% of the time. The tab is created, but the main Winbox window is never brought inside.
edited by bstaggs on 10/20/2014