By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
428,558 Members | 1,533 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 428,558 IT Pros & Developers. It's quick & easy.

Deploy ASP.NET 1.1 project on live sites

P: n/a
I have a ASP.NET 1.1 project that I want to be able to deploy on my web-servers
while they have real traffic (40 requests/second).

When I copy the projects assembly in the bin-directory of the website directory
the application gets restarted and the web server needs to recompile all
my aspx-pages. Because the traffic is high the web server needs to recompile
a lot of aspx-pages at the same time.
Because of this alot of requests gets queued and I get so me "Server too
busy" errors (because the queue got full).

What are the best practices for deployment on these kinds of scenarios? I
want do minimize the delay the users get when I deploy a new version.

I have a web garden (2 worker processes) on each web server (because I want
increased stability). Is it true that I need to compile each page twice if
I have 2 worker processes?
Is it necessary to have 2 worker processes if stability is not a problem?

/nisse
Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi Nisse,

Welcome to ASPNET newsgroup.
As for the questions with deploying updating components in asp.net web
application, here are some of my understanding and suggestions:

Generally all the private components(non- strong named) are all put in the
private bin dir, and when there occur any modificatio in the bin dir, the
application's running appDomain will restart. And during the reinitilize
of the new appdomain, there'll occur some operations , such as the
recompilation of the dynamic pages or components you mentioned, also the
runtime will shadow copy some of the used private assemlies. And such
dynamic compiled assmelies or shadow copied ones's target location is also
appDomain specific (the target temp dir), so in WebGarden scenario, whether
each appdomain in separate process will need to dynamically recompile the
pages or shadow copy the components also depend on the internal
implemenation(whether they'll share the same dynamic code generation or
shadow copy temp dir location). IMO, I think the current implemenation
will share such setting for each application so as to avoid additional
overhead, but the reload of each appdomain in multi asp.net process is
unavoidavable.

In addition, for webgarden, if not necessary( for stability), of course we
recommend that we avoid using it since web garden or other webfarm (loading
balance ...) will cause problems for state management such as the
Inproc session , Applicaiton in memory datas( the Asp.net Cache
collection... ).

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


--------------------
| Message-ID: <ab*************************@msnews.microsoft.co m>
| From: =?iso-8859-1?Q?Nils=20Hedstr=f6m?= <Ni***@online.nospam>
| Subject: Deploy ASP.NET 1.1 project on live sites
| MIME-Version: 1.0
| Content-Transfer-Encoding: 8bit
| Content-Type: text/plain; charset=iso-8859-1; format=flowed
| X-Newsreader: JetBrains Omea Reader 671.6
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| Date: Wed, 21 Sep 2005 09:49:29 -0700
| NNTP-Posting-Host: static-213-115-146-117.sme.bredbandsbolaget.se
213.115.146.117
| Lines: 1
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msft ngp13.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.aspnet:126175
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| I have a ASP.NET 1.1 project that I want to be able to deploy on my
web-servers
| while they have real traffic (40 requests/second).
|
| When I copy the projects assembly in the bin-directory of the website
directory
| the application gets restarted and the web server needs to recompile all
| my aspx-pages. Because the traffic is high the web server needs to
recompile
| a lot of aspx-pages at the same time.
| Because of this alot of requests gets queued and I get so me "Server too
| busy" errors (because the queue got full).
|
| What are the best practices for deployment on these kinds of scenarios? I
| want do minimize the delay the users get when I deploy a new version.
|
| I have a web garden (2 worker processes) on each web server (because I
want
| increased stability). Is it true that I need to compile each page twice
if
| I have 2 worker processes?
| Is it necessary to have 2 worker processes if stability is not a problem?
|
| /nisse

|
|

Nov 19 '05 #2

P: n/a
Hi Nisse,

How are you doing on this issue and does the things in my last reply helps
a littile. If there're any further questions or anything else we can help,
please feel free to post here.

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

--------------------
| X-Tomcat-ID: 51533423
| References: <ab*************************@msnews.microsoft.co m>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: st*****@online.microsoft.com (Steven Cheng[MSFT])
| Organization: Microsoft
| Date: Thu, 22 Sep 2005 03:15:26 GMT
| Subject: RE: Deploy ASP.NET 1.1 project on live sites
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| Message-ID: <d4*************@TK2MSFTNGXA01.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| Lines: 89
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.aspnet:126299
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Hi Nisse,
|
| Welcome to ASPNET newsgroup.
| As for the questions with deploying updating components in asp.net web
| application, here are some of my understanding and suggestions:
|
| Generally all the private components(non- strong named) are all put in
the
| private bin dir, and when there occur any modificatio in the bin dir, the
| application's running appDomain will restart. And during the reinitilize
| of the new appdomain, there'll occur some operations , such as the
| recompilation of the dynamic pages or components you mentioned, also the
| runtime will shadow copy some of the used private assemlies. And such
| dynamic compiled assmelies or shadow copied ones's target location is
also
| appDomain specific (the target temp dir), so in WebGarden scenario,
whether
| each appdomain in separate process will need to dynamically recompile the
| pages or shadow copy the components also depend on the internal
| implemenation(whether they'll share the same dynamic code generation or
| shadow copy temp dir location). IMO, I think the current implemenation
| will share such setting for each application so as to avoid additional
| overhead, but the reload of each appdomain in multi asp.net process is
| unavoidavable.
|
| In addition, for webgarden, if not necessary( for stability), of course
we
| recommend that we avoid using it since web garden or other webfarm
(loading
| balance ...) will cause problems for state management such as the
| Inproc session , Applicaiton in memory datas( the Asp.net Cache
| collection... ).
|
| Thanks,
|
| Steven Cheng
| Microsoft Online Support
|
| Get Secure! www.microsoft.com/security
| (This posting is provided "AS IS", with no warranties, and confers no
| rights.)
|
|
|
|
|
|
| --------------------
| | Message-ID: <ab*************************@msnews.microsoft.co m>
| | From: =?iso-8859-1?Q?Nils=20Hedstr=f6m?= <Ni***@online.nospam>
| | Subject: Deploy ASP.NET 1.1 project on live sites
| | MIME-Version: 1.0
| | Content-Transfer-Encoding: 8bit
| | Content-Type: text/plain; charset=iso-8859-1; format=flowed
| | X-Newsreader: JetBrains Omea Reader 671.6
| | Newsgroups: microsoft.public.dotnet.framework.aspnet
| | Date: Wed, 21 Sep 2005 09:49:29 -0700
| | NNTP-Posting-Host: static-213-115-146-117.sme.bredbandsbolaget.se
| 213.115.146.117
| | Lines: 1
| | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msft ngp13.phx.gbl
| | Xref: TK2MSFTNGXA01.phx.gbl
| microsoft.public.dotnet.framework.aspnet:126175
| | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
| |
| | I have a ASP.NET 1.1 project that I want to be able to deploy on my
| web-servers
| | while they have real traffic (40 requests/second).
| |
| | When I copy the projects assembly in the bin-directory of the website
| directory
| | the application gets restarted and the web server needs to recompile
all
| | my aspx-pages. Because the traffic is high the web server needs to
| recompile
| | a lot of aspx-pages at the same time.
| | Because of this alot of requests gets queued and I get so me "Server
too
| | busy" errors (because the queue got full).
| |
| | What are the best practices for deployment on these kinds of scenarios?
I
| | want do minimize the delay the users get when I deploy a new version.
| |
| | I have a web garden (2 worker processes) on each web server (because I
| want
| | increased stability). Is it true that I need to compile each page twice
| if
| | I have 2 worker processes?
| | Is it necessary to have 2 worker processes if stability is not a
problem?
| |
| | /nisse
|
| |
| |
|
|

Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.