optimizing aspnet application - speed up

Hi
I noticed that all my ASPNET applications (+ MSSQL Server - I checked the
database and it is ok) run very slowly (especially from the beginning). I
made comparison to other applications (not mine) on another servers. I
wonder how could I boost the applications. The only thing I suspect is that
in configuration manager in my VS2003 I have got debug.
Could you tell me your suggestions please?
Regards
Darek T.Create a simple one line test.aspx page
<% response.write ("hello world") %>
and go from there
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:OtjQSbOXGHA.4920@.TK2MSFTNGP02.phx.gbl...
> Hi
> I noticed that all my ASPNET applications (+ MSSQL Server - I checked the
> database and it is ok) run very slowly (especially from the beginning). I
> made comparison to other applications (not mine) on another servers. I
> wonder how could I boost the applications. The only thing I suspect is
> that in configuration manager in my VS2003 I have got debug.
> Could you tell me your suggestions please?
> Regards
> Darek T.
>
With VS 2005 you can minimize it a little, but the first time the page is
render in a session it will be a slower, after that it is pretty fast. To
speed things up a little, look into deploying your ASP 2.0 app using a
pre-compile approach
aspnet_compiler -v [Application Name} -p[Physical location] [Target}
Your aspx files are now just headers -- you can rename HTML, XML, XSD,
web.config and Text files to .aspx to take advantage of the obfuscating
also. Runs faster overall.
Rob
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:OtjQSbOXGHA.4920@.TK2MSFTNGP02.phx.gbl...
> Hi
> I noticed that all my ASPNET applications (+ MSSQL Server - I checked the
> database and it is ok) run very slowly (especially from the beginning). I
> made comparison to other applications (not mine) on another servers. I
> wonder how could I boost the applications. The only thing I suspect is
> that in configuration manager in my VS2003 I have got debug.
> Could you tell me your suggestions please?
> Regards
> Darek T.
>
Nice joke ... really.
"Jeff Dillon" <jeffdillon@.hotmail.com> wrote in message
news:OXkxgpOXGHA.4120@.TK2MSFTNGP03.phx.gbl...
> Create a simple one line test.aspx page
> <% response.write ("hello world") %>
> and go from there
> "Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
> news:OtjQSbOXGHA.4920@.TK2MSFTNGP02.phx.gbl...
>
There's lots of things you can take advantage of to make things run
faster. Are you using Page and Application Caching, effective
ViewState & Session usage
Things will always initially be slow. If the ASP.NET pages have
changed then they will need to be loaded into memory and re-compiled
(due to on-demand dynamic compilation)
If you're using IIS6 you can increase the recycle timeout to prevent
asp.net from being recycled and hence having to recomple after
restarting.
I've seen it suggested that you should use a script to automatically
call the popular pages in your application as soon as you deploy new
versions so that the first visitors don't experience the delay
Also, have you added Trace="True" to your Page Directive to get a
better idea of timings?
Finally, I've used ANTS Profiler from www.red-gate.com to get an exact
idea of which methods are taking time and how often they get called.
Redgate also have ANTS Loads to stress test web apps. The Profiler
saved me days in trying to tune .Net apps
Jason
I wasn't joking! This would tell if the server itself was slow. Start with a
simple page (basic troubleshooting) then add your code till you find the
problem.
Jeff
"Dariusz Tomon" <d.tomon@.mazars.pl> wrote in message
news:Oyh0aDPXGHA.4424@.TK2MSFTNGP05.phx.gbl...
> Nice joke ... really.
> "Jeff Dillon" <jeffdillon@.hotmail.com> wrote in message
> news:OXkxgpOXGHA.4120@.TK2MSFTNGP03.phx.gbl...
>