Temporary VB.net Application Slowdown after Deployment

Hi,

I am having a problem with a VB.net application. Whenever I deploy a new version of the website to the servers they seem to lock up/slow down terribly for about an hour or so. Eventually they sort themselves out and return to normal. This has only happened very recently and only with certain websites running from one IIS.

I'm not sure whether this helps but in order to deploy I am deleting everything except the web.config and then copying the new web folder over the top. Should we be restarting IIS before doing this? I am reluctant to do so as we have many websites running from IIS and this would then bring them all down.

Has anyone else seen a problem of this type?

Thanks in advance,
Paul.
han11onAsked:
Who is Participating?
 
lostcarparkCommented:
I agree with the above comments about compiling for release before deploying on the server. We found our apps were consuming server resources at a crazy rate because we'd deployed debug versons instead of release.

To do this, go to the project in Visual Studio and change the properties from Debug to Release. Then Build the solution and copy to the web server. There should be no need to delete the previous version before copying. You also shouldn't put any of your .vb files on the server. The .aspx files, the \bin directory, and any image files should be all you need.

One reason for the slowdown may be the Just-In-Time compilation of the intermediate P-Code. .NET binaries are not true compiled code. The first time you reference a module it will need to compile it in memory. When you migrate your project, the first thing you should do is visit every page in the site so that all the compilation will be completed, then your site should run properly.

ASP.NET 2.0 gives you the option of precompiling evreything, which should remove the initial delay when a module is loaded.
0
 
awaiskhanCommented:
please use the release version for deployment.

Cheers

0
 
MsShadowCommented:
- Compile for Release
- Copy the website

Imho restart IIS. Or at least go to the virtual directory you are using and recreate the Application in your IIS manager.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
GarylsCommented:
Yea Compile for release (or publish as its now called?)

You should not need to Restart IIS but if you're having problems it can help.

Also, check how many RAM is free.... I had a nightmare with a server running very slow due to low RAM. I needed around 150mb (minimum) free for it to just function.
0
 
han11onAuthor Commented:
Hi,

Thanks everyone for the help! We have always only installed Release versions (just dlls and aspx without vb) anyway.

However I think we may be onto something about the pre-compiling of code. I am not using vs2005 (plan to upgrade soon) though so would this still be the case with vs 2003? ie do i need to specify somewhere in the project to pre-compile or will this happen by default?

Cheers,
Paul.
0
 
lostcarparkCommented:
Hi Paul,

You can use the aspnet_compiler utility to precompile your applicatoin under ASP.NET 2.0. You can find details of the syntax here:

http://www.odetocode.com/Articles/417.aspx

Regards,

James
0
 
han11onAuthor Commented:
Hi,

I think the problem may have been due to the Just-in-time compilation of the P-Code. Sorry James I was trying to work out how to split the points as I also found that "Precompilation" article very interesting and useful!

Cheers,
Paul.
0
 
MsShadowCommented:
Can you test that when you don't use the webapplication for 1-2 days the same things happens? Cause then it might be your .net runtime.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.