ANTS Memory Profiler - IIS(6.0) : Problem

Memory profiling for .NET developers

Moderators: Luke Jefferson, StephenC, AndrewH, melvyn.harbour, james.billings, Laura Morley, dene.boulton

ANTS Memory Profiler - IIS(6.0) : Problem

Postby erhu » Mon Aug 06, 2012 12:15 pm

Hi,

I've started evualating your product (ANTS Memory Profiler 7.4) last week and I'm encountering few problems with it..

First and majour problem which I'm having is one that seems to be an old case. Is to start profiling and process hangs on big red notification \"Starting application...\". This happens when I select:
#1 [ASP.NET web application (IIS)]
#1.1 url: \"http://localhost:81\"
#1.2 [Profile child processes]
#1.3 [Monitor disposal of objects]
#1.4 [Original port (IIS will restart)]
#1.5 [ ::: Start Profiling ::: ]

Process seems to flow correctly, but I'm not able to take snapshot as the above mentioned red text hangs on the screen. If I close the browser, the process seems to end correctly also... (I doubt that this is the way it's supposed to work,.. right? not at least as is described in the demo video... heh)

Also the logs look weird:
    06 Aug 2012 13:42:49.963 [1] INFO RedGate.Profiler.Logging.LogService - Starting new ANTS Memory Profiler 7 session
    06 Aug 2012 13:42:49.963 [1] INFO RedGate.Profiler.Logging.LogService - Assembly version: 7.4.0.41
    06 Aug 2012 13:42:55.081 [1] WARN RedGate.Profiler.OS.Local.LocalWindowsVersionInspector - Detected Windows version: Windows Server 2003 Enterprise (5.2 32-bit Server)
    06 Aug 2012 13:42:55.081 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - IIS is supported on installed OS version
    06 Aug 2012 13:42:55.190 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Result of check to see if inetinfo.exe running: True
    06 Aug 2012 13:42:55.190 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Checks confirm that IIS is running.
    06 Aug 2012 13:42:55.190 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Checks confirm that IIS is enabled.
    06 Aug 2012 13:42:55.190 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Successfully detected IIS installation: IIS 6 (Auto-detected)
    06 Aug 2012 13:42:55.190 [1] WARN RedGate.Profiler.IISSupport.Local.LocalIisInspector - Checks confirm that IIS is installed.
    06 Aug 2012 13:43:51.912 [6] WARN RedGate.Profiler.IISSupport.SharePointHelper - SharePoint version: none found (looking for 2010 or 2007 using registry keys)
    06 Aug 2012 13:44:05.044 [17] INFO RedGate.Profiler.Engine.Logger - ANTS Memory Profiler Engine has started.
    06 Aug 2012 13:44:05.060 [17] INFO RedGate.Profiler.Engine.Logger - Version: 7.4.0.41
    06 Aug 2012 13:44:05.060 [17] INFO RedGate.Profiler.Engine.Startup.Basic.PipeConnection - Listening for connections on \\\\.\\pipe\\AMP72.
    06 Aug 2012 13:44:05.326 [24] INFO RedGate.Profiler.Engine.Startup.Sessions.BaseSession - InetSrv directory is C:\\Windows\\system32\\inetsrv
    06 Aug 2012 13:44:05.326 [24] INFO RedGate.Profiler.Engine.Startup.Sessions.BaseSession - Trying to start the IIS profiler service
    06 Aug 2012 13:44:05.326 [24] INFO RedGate.Profiler.Engine.Startup.Sessions.BaseSession - The IIS service appears to be registered; requesting that it start now
    06 Aug 2012 13:44:10.601 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.601 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.601 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.601 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.601 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.601 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.601 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.616 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.616 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81
    06 Aug 2012 13:44:10.616 [24] WARN RedGate.Profiler.Engine.Startup.IIS.IISUtilities - WaitForPort on address 127.0.0.1, port 81


Any help would be appreciated.

Also the application loads unusually slow.. it takes around 1min to load splash screen and +2 min to load the \"main view\" of the application...
(W2k3SP2~VM, 4GB, x86, Xeon L5420@2.5GHz)
erhu
 
Posts: 5
Joined: Mon Aug 06, 2012 12:01 pm

Postby james.billings » Tue Aug 07, 2012 3:11 pm

Thanks for that - the log entry suggests that the profiler maybe isn't getting as far as fully connecting to the process. There's a couple of troubleshooting steps which can sometimes yield more success:

- ensure you start the profiler elevated by locating the .exe and then right-clicking and picking "Run as Administrator"
- if possible, try using the local webdev server instead of IIS to see if it behaves differently

It doesn't sound like the profiled application is actually crashing; so it's a little harder to work out what may be going wrong. You can also try the attach to process option to see if this works any better?
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.

Re:

Postby erhu » Wed Aug 08, 2012 8:08 am

james.billings wrote:Thanks for that - the log entry suggests that the profiler maybe isn't getting as far as fully connecting to the process. There's a couple of troubleshooting steps which can sometimes yield more success:

- ensure you start the profiler elevated by locating the .exe and then right-clicking and picking "Run as Administrator"
- if possible, try using the local webdev server instead of IIS to see if it behaves differently

It doesn't sound like the profiled application is actually crashing; so it's a little harder to work out what may be going wrong. You can also try the attach to process option to see if this works any better?


Hi and thank you for your answer.

I just noticed that yesterday after 28hours (after started profiling) the process flow actually continued.... It worked fine and everything but there was a crash on w3wp process on the way and the site was reloaded, as we as the w3wp also, but the ANTS Mem.prof. application started it again... so, your answer is actullay some what correct, but now the problem has changed to another. To application is ridiculously slow... I also noticed that the application runs way faster on my local laptop than on the server, which is around 5times faster (or something)...

Profiling seems to be possible, but it's just ridiculously slow... also after first w3wp process chrash the shanpshot function fails (something: "the process is not running"; but the snapshot is taken and data received regardless of message)...

Conclution:
If someone finds a way to make it work a bit faster than 28 hours then I would be glad. :-)

Br
erhu
 
Posts: 5
Joined: Mon Aug 06, 2012 12:01 pm

Postby james.billings » Wed Aug 08, 2012 12:17 pm

I've not heard of it being as slow as this. Profiling does obviously introduce an overhead, but that seems unusually slow. Does turning off "Monitoring of Disposed Objects" have any effect?

Also, are there any messages in the windows event log that may give further clues?
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.

Re:

Postby erhu » Tue Aug 14, 2012 11:04 am

james.billings wrote:I've not heard of it being as slow as this. Profiling does obviously introduce an overhead, but that seems unusually slow. Does turning off "Monitoring of Disposed Objects" have any effect?

Also, are there any messages in the windows event log that may give further clues?


Disabling this function didn't have any effect.

Windows Events doesn't have any noticeable log, that would have any references point to it to be this slow.

I have tried another software that had much bigger sys.req. than this and it launched faster and worked averagely better, though the usage was worse and was not as versatile as AMP7.

Just that the start and profiling initiation are redicilously slow and also some graphs that were large.
erhu
 
Posts: 5
Joined: Mon Aug 06, 2012 12:01 pm

Postby james.billings » Tue Aug 14, 2012 11:08 am

Thanks for that, and sorry it's not helped.

Do you know how much memory your application uses once started in normal use?

I'm wondering if you're simply running out of RAM - once the profiler has to page to disk for the information, performance will drop off quite noticeably. If you have a 64-bit machine with more RAM in it that you could test on, it may be worth trying?
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.

Re:

Postby erhu » Wed Aug 15, 2012 7:44 am

james.billings wrote:Thanks for that, and sorry it's not helped.

Do you know how much memory your application uses once started in normal use?

I'm wondering if you're simply running out of RAM - once the profiler has to page to disk for the information, performance will drop off quite noticeably. If you have a 64-bit machine with more RAM in it that you could test on, it may be worth trying?



On AMP7 start
- before Splash; for 3min: < 10MB
- after Splash; for +2min: < 40MB
- on profiling settings view after start: < 80MB
(handles & threads at above: ~730/30)

About the RAM, I tought so too at first so we added 2G without any result..
System is VM 2k3Server -32bit
We haven't tried yet on 64bit..
(just that current case of problem needed to be solved is on 2k3-32bit)
erhu
 
Posts: 5
Joined: Mon Aug 06, 2012 12:01 pm

Postby james.billings » Wed Aug 15, 2012 8:16 am

That doesn't sound like it's using up a huge amount of memory. The other thing that can potentially slow down the profiler is a huge number of objects for it to process but there's no simple way to diagnose this. If another application with higher requirements starts faster, it suggests the problem is specific to whatever the problem app does during startup maybe. We'd ideally need a copy here to troubleshoot on, but i'm not sure how easy that is to supply?
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.

Re:

Postby erhu » Wed Aug 15, 2012 11:38 am

james.billings wrote:That doesn't sound like it's using up a huge amount of memory. The other thing that can potentially slow down the profiler is a huge number of objects for it to process but there's no simple way to diagnose this. If another application with higher requirements starts faster, it suggests the problem is specific to whatever the problem app does during startup maybe. We'd ideally need a copy here to troubleshoot on, but i'm not sure how easy that is to supply?


On my "local" laptop (elitebook 8560w) it runs on a snap (quick). Problem is that I can't test anything from it... (need to run it from server).

Just that evaluation time is ending and I just had only problems with this software. Regarding to events spoken above. :(
erhu
 
Posts: 5
Joined: Mon Aug 06, 2012 12:01 pm

Postby james.billings » Mon Aug 20, 2012 9:02 pm

Hmm, if it's quick on the local machine, then it's more likely some problem specific to the server you're trying on; however i'm not sure what that would be- is the server that's slow under load from other applications maybe (cpu usage etc?) Or is the application itself being tested differently (i.e. in production use on the server but only you testing it on the development laptop)?
james.billings
 
Posts: 1144
Joined: Wed Jun 16, 2010 11:10 am
Location: My desk.


Return to ANTS Memory Profiler 7

Who is online

Users browsing this forum: No registered users and 0 guests