Last post Aug 12, 2005 07:10 PM by smcmiata
Aug 05, 2005 11:17 AM|smcmiata|LINK
Aug 05, 2005 04:53 PM|narayanas|LINK
Aug 05, 2005 05:10 PM|smcmiata|LINK
Two possibilities occur to my mind;
1. It could be due to exceeding no of concurrent connection or
2. It could be due to some bad coding practices which might have resulted in some memory leaks.
You could try and use CLR Profiler/ASP.NET Profiler to nail down the culprit which is eating away lof of memory.
Aug 06, 2005 01:11 AM|narayanas|LINK
1. If you are using VS.NET Enterprise Editon or VS.NET Enterprise Architect Edition you can make use of Application Test Center 2000 to check the what is the limit of no concurrent connection? or You can use any of the Web Stress testing tools to find out
2. W.r.t the bad coding, you could use ASP.NET profiler or CLR profiler and it provies which methods/calls are eating up memory.
Wish this will help you. Just in case you need any further help, please post it back.
Aug 09, 2005 01:05 PM|smcmiata|LINK
Aug 09, 2005 04:45 PM|smcmiata|LINK
Aug 11, 2005 05:06 PM|narayanas|LINK
Aug 11, 2005 05:53 PM|smcmiata|LINK
To create sample console applications for profiling
csc /t:exe /out:ProfilerSample1.exe ProfilerSample1.cs
csc /t:exe /out:ProfilerSample2.exe ProfilerSample2.cs
My system doesn't know what "csc" is. So then I tried running the CLR for my website, but nothing worked.Help!Sean
Aug 11, 2005 07:36 PM|narayanas|LINK
I know what is happening.....
1. You need not have to do anything with ProfilerSample1.cs and you need not have to compile this from the commandline in your context. It is only a sample provided in the article.
2. Goto VS.NET/ Visual Studi.NET Tools/ Visual Studio.NET 2003 Command Prompt
When you type CSC from the commandline it should recongnize "CSC" now.
having said that, did you try the following;
Note Sometimes the current version of the tool does not respond to the page load in Step 4. If this problem occurs, try changing the ASP.NET process identity to
SYSTEM in the <ProcessModel> element in Machine.config. After you finish profiling your application, be certain that you change the application's identity back to
BTW: Are you getting any specific message while trying to run CLR Profiler?
Aug 11, 2005 07:50 PM|smcmiata|LINK
Aug 11, 2005 10:13 PM|narayanas|LINK
Aug 12, 2005 12:55 PM|smcmiata|LINK
"Waiting for ASP.NET to start common laguage runtime - this is the time to load your test page." (it also had a cancel button)
I opened my brower (IE 6) and then opened my .aspx test page. Ran the simple button/text I had on it. But when I go back to the CLR, there is no "Kill ASP.NET" option. The "Kill Application" button is greyed out.
I did a search for machine.config, and could not find one on my PC.
Aug 12, 2005 02:39 PM|narayanas|LINK
Aug 12, 2005 03:11 PM|smcmiata|LINK
Aug 12, 2005 04:12 PM|smcmiata|LINK
Aug 12, 2005 07:10 PM|smcmiata|LINK