Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare - Knowledgebase Articles > Performance Tips for Internet Sessions

Performance Tips for Internet Sessions

Table of contents

Updated April 13th, 2017


Over The Internet (OTI) is used for slow-speed and high-latency level links. Adjusting Internet Session settings can be effective on slow performing connections. In cases of high-speed links but low-speed latencies, OTIs results are subjectively slower than normal MRC sessions (not Internet).


All DameWare Mini Remote Control versions


Below are a few tips to enhance OTI performance:


  • Unique configurations may have negative effects on connection performance.
  • Signal packets are sent too frequently when RTT from Agent using proxy is more than a few milliseconds (ms). SignalR message is only sent once per 100ms when buffers are added, which may help in high SignalR overhead.
  • Some older Operating Systems such as XP and Windows 2008 sleep for longer periods. For example, buffering delays for those OSs may be at 800ms. The expected maximum delay is at 100ms.
  • RDP is sometimes used in parallel with MRC sessions. RDP uses a lot of bandwidth, which can result in reduced MRC connection performance.


Note: Simultaneous use of RDP to the machine where the Internet Session agent is also installed is not recommended. This will result in a reduced user experience.


Having roles like technician console, Proxy, or End User Agent in VMs may cause latency. Using the newest Agent version minimizes this issue to a latency of about 1.5s.


A refresh delay is a fixed minimum delay between two (2) consecutive refreshes of the screen. This is used to limit the amount of data sent by the Agent at the cost of fluency and continuity of motions. Users can adjust settings of the refresh Delay in Internet Session and DMRC Minor Driver settings.

  • Adjust the default configuration settings to tune bandwidth.
  • Add buffers to Agent's SignalR interface.
  • Calculate real-time clock instead of the number of sleeps for Windows XP, 2008 and older.
  • Shut down Remote Desktop Protocol (RDP).
  • Use the newest Agent version.
  • Use of refresh delay.



Settings for Refresh Delay on Internet Sessions need to be applied on every new session.


The quality of high-speed links (1000ks/s) on remote sessions with lower delay value of 100ms is better compared to delay value of 500ms.


For high-speed links, delay values should be decreased. The Appropriate value of the delay may be determined by the user by observing behavior.


Delays are configured from the Host Properties dialog available in the Context menu for the host as Settings menu.


See the following images from the MRC application:




Last modified