Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio 2010 remote debugging is very slow (across domains, over VPN)

Overall debugging works, but each step through code takes dozens of seconds.

I've already closed all additional windows like stack trace, watches, autos; deleted all breakpoints.

The server and development machine are located in different domains, so I set up a local user on both, with a matching password. The remote debugger is running as a service.

Looking at the security log, I found quite a lot of entries about remote debugging account logging in (record about every minute).

Any suggestions on how I can speed up remote debugging?

  • Development computer: quad core, 8 GB memory, Windows 7 x64, Visual Studio 2010 Ultimate.
  • Target server: ASP.NET website, 2x dual core Xeon, 2 GB memory, remote debugger 2010.
  • Communication channel: VPN, 5 Mbit/s, latency about 20 ms. (it seems that debugging never uses more than 20 kbyte/s)
like image 714
alex Avatar asked May 05 '10 17:05

alex


People also ask

How to Configure Firewall for remote debugging?

If you can't attach to your app with the remote debugger, make sure the remote debugging firewall ports, protocols, network types, and app settings are all correct. In the Windows Start menu, search for and open Windows Firewall, and select Allow an app through Windows Firewall.

How to do remote debugging using Visual Studio?

Select Configure remote debugging to configure the firewall and start the remote debugger. When configuration is complete, the Remote Debugger window appears. The remote debugger is now waiting for a connection. Use the server name and port number shown to set the remote connection configuration in Visual Studio.

How do I disable remote debugging in Visual Studio?

05 On the General settings panel, under Debugging, select Off next to Remote debugging setting to disable remote debugging using Microsoft Visual Studio for the selected Azure App Services web application. Click Save to apply the changes.


1 Answers

First identify the overall response times. It may be a little bit low level, but get Wireshark and monitor communication between both servers. That way you will know if debugging is slow because of your network and will give you a starting point.

Turn off active mode, else you may raise a few alarms in your network. I used it to debug communication between our WFE and a FAST query server, and we detected where the problem was.

like image 172
xmorera Avatar answered Oct 04 '22 06:10

xmorera