Why is "Attach to Process" in Visual Studio 2012 to w3wp.exe so slow?

Question

When debugging an IIS web application that connects to the w3wp.exe workflow process, it takes several minutes to load a large number of DLL files, every few seconds. The machine is running Windows 8 with 8 cores and 16 GB of RAM, so there is really no limitation on the machine.

He makes attachment to the process of such a painful procedure.

Just a sample from the output window:

'w3wp.exe' (Managed (v4.0.30319)): Loaded 'Anonymously Hosted DynamicMethods Assembly' 'w3wp.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data.OracleClient\v4.0_4.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll', Symbols loaded. 'w3wp.exe' (Managed (v4.0.30319)): Loaded 'EntityFrameworkDynamicProxies-audits.core' 'w3wp.exe' (Managed (v4.0.30319)): Loaded 'C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.WindowsAzure.ServiceRuntime\v4.0_2.1.0.0__31bf3856ad364e35\Microsoft.WindowsAzure.ServiceRuntime.dll' 

Is it slow for anyone else, if not, what can be done to increase productivity?

Answer 1

I know this is pretty old, but I think your problem is all downloadable characters that you really don't need (but might want).

You can significantly reduce the number of characters loaded with (un) to configure a pair of parameters:

 Tools | Options | Debugging | General - check "Enable Just My Code" Tools | Options | Debugging | Symbols - uncheck "Microsoft Symbol Servers"