I'm trying to profile our server process, which runs on a beefy server with 16 CPU cores and 32 Gig memory, of which about 8-22 Gigs (dynamically changing, up and down) is used by our .NET process during a certain operation that we wish to investigate.
Is there any way I can profile this process? Is this a hard coded adress space cap or is there a workaround to allow the profiler to consume more memory? We have plenty of unused physical memory available on the box.
The application is a WCF Service server hosted by IIS 7 using .NET 4.0 and EF 4.0, among other libraries. The server is a Windows Server 2008 R2, version 6.1.7601 SP1 Build 7601.
We are using licensed versions of ANTS Memory Profiler 188.8.131.52.