Web Server Performance

We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
Web Application ( in the same application Pool).
Each instance connects to a SQL 2K database on a separate database server.
The database size is around 100 MB (min ) to 3 GB Max.
The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
The database server is a dual proc Xeon with 4 GB of Ram.
Each instance of the Web Application has an average of 15 users.
We reboot the servers every wend.
I have set the Worker Process to recycle at 4 AM everyday.
The problem is that our clients often receive Out Of Memory exceptions.
Task
Manager doesn't show any abnormal activity.
The Memory Utilization on the web server seems to be around 500 MB .. which
should be fine for a 2 GB RAM system that is used solely as a web server.
My questions:
1 Are we overloading the server. ?
2 What tweaks or configuration changes can we do to improve performance.
Thanks,
Sachin SalgarkarSachin,
Sometimes it can be something as simple as changing the
connectionstring to the database slightly to improve pooling, or ensuring
that the garbage collection is happening correctly. Even though .Net is
managed, garbage collection should still be written to handle the closing of
datareaders/connections and disposing of them properly. That helps free up
their resources quickier.
MS released a great book in their patterns and practices called Improving
.Net Application Performance and Scalability. You don't have to buy it
though as they also made a downloadable PDF version at:
http://msdn.microsoft.com/library/d...n
et.asp
This has a good number of well-organized do's and dont's that would let you
dig through and check to see if there is something going on in your code
that could be altered or some setting that could be tweaked to avoid your
issues.
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199...2006
"Sachin Salgarkar" <sachin@.aegiscommerce.com> wrote in message
news:uN7rUpG7GHA.4552@.TK2MSFTNGP05.phx.gbl...
> We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
> Web Application ( in the same application Pool).
> Each instance connects to a SQL 2K database on a separate database server.
> The database size is around 100 MB (min ) to 3 GB Max.
> The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
> The database server is a dual proc Xeon with 4 GB of Ram.
> Each instance of the Web Application has an average of 15 users.
> We reboot the servers every wend.
> I have set the Worker Process to recycle at 4 AM everyday.
> The problem is that our clients often receive Out Of Memory exceptions.
> Task
> Manager doesn't show any abnormal activity.
> The Memory Utilization on the web server seems to be around 500 MB ..
> which
> should be fine for a 2 GB RAM system that is used solely as a web server.
> My questions:
> 1 Are we overloading the server. ?
> 2 What tweaks or configuration changes can we do to improve performance.
> Thanks,
> Sachin Salgarkar
>
Thanks Mark.
-Sachin
"Mark Fitzpatrick" <markfitz@.fitzme.com> wrote in message
news:uVUhZxG7GHA.2380@.TK2MSFTNGP02.phx.gbl...
> Sachin,
> Sometimes it can be something as simple as changing the
> connectionstring to the database slightly to improve pooling, or ensuring
> that the garbage collection is happening correctly. Even though .Net is
> managed, garbage collection should still be written to handle the closing
> of datareaders/connections and disposing of them properly. That helps free
> up their resources quickier.
> MS released a great book in their patterns and practices called Improving
> .Net Application Performance and Scalability. You don't have to buy it
> though as they also made a downloadable PDF version at:
> http://msdn.microsoft.com/library/d...br />
enet.asp
> This has a good number of well-organized do's and dont's that would let
> you dig through and check to see if there is something going on in your
> code that could be altered or some setting that could be tweaked to avoid
> your issues.
>
> --
> Hope this helps,
> Mark Fitzpatrick
> Former Microsoft FrontPage MVP 199...2006
> "Sachin Salgarkar" <sachin@.aegiscommerce.com> wrote in message
> news:uN7rUpG7GHA.4552@.TK2MSFTNGP05.phx.gbl...
>

Web Server Performance

We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
Web Application ( in the same application Pool).
Each instance connects to a SQL 2K database on a separate database server.
The database size is around 100 MB (min ) to 3 GB Max.
The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
The database server is a dual proc Xeon with 4 GB of Ram.
Each instance of the Web Application has an average of 15 users.

We reboot the servers every weekend.
I have set the Worker Process to recycle at 4 AM everyday.

The problem is that our clients often receive Out Of Memory exceptions.
Task
Manager doesn't show any abnormal activity.
The Memory Utilization on the web server seems to be around 500 MB .. which
should be fine for a 2 GB RAM system that is used solely as a web server.
My questions:
1 Are we overloading the server. ?
2 What tweaks or configuration changes can we do to improve performance.

Thanks,
Sachin SalgarkarSachin,
Sometimes it can be something as simple as changing the
connectionstring to the database slightly to improve pooling, or ensuring
that the garbage collection is happening correctly. Even though .Net is
managed, garbage collection should still be written to handle the closing of
datareaders/connections and disposing of them properly. That helps free up
their resources quickier.

MS released a great book in their patterns and practices called Improving
..Net Application Performance and Scalability. You don't have to buy it
though as they also made a downloadable PDF version at:
http://msdn.microsoft.com/library/d...ml/scalenet.asp
This has a good number of well-organized do's and dont's that would let you
dig through and check to see if there is something going on in your code
that could be altered or some setting that could be tweaked to avoid your
issues.

--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006

"Sachin Salgarkar" <sachin@.aegiscommerce.comwrote in message
news:uN7rUpG7GHA.4552@.TK2MSFTNGP05.phx.gbl...

Quote:

Originally Posted by

We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
Web Application ( in the same application Pool).
Each instance connects to a SQL 2K database on a separate database server.
The database size is around 100 MB (min ) to 3 GB Max.
The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
The database server is a dual proc Xeon with 4 GB of Ram.
Each instance of the Web Application has an average of 15 users.
>
We reboot the servers every weekend.
I have set the Worker Process to recycle at 4 AM everyday.
>
The problem is that our clients often receive Out Of Memory exceptions.
Task
Manager doesn't show any abnormal activity.
The Memory Utilization on the web server seems to be around 500 MB ..
which
should be fine for a 2 GB RAM system that is used solely as a web server.
My questions:
1 Are we overloading the server. ?
2 What tweaks or configuration changes can we do to improve performance.
>
Thanks,
Sachin Salgarkar
>

Thanks Mark.

-Sachin

"Mark Fitzpatrick" <markfitz@.fitzme.comwrote in message
news:uVUhZxG7GHA.2380@.TK2MSFTNGP02.phx.gbl...

Quote:

Originally Posted by

Sachin,
Sometimes it can be something as simple as changing the
connectionstring to the database slightly to improve pooling, or ensuring
that the garbage collection is happening correctly. Even though .Net is
managed, garbage collection should still be written to handle the closing
of datareaders/connections and disposing of them properly. That helps free
up their resources quickier.
>
MS released a great book in their patterns and practices called Improving
.Net Application Performance and Scalability. You don't have to buy it
though as they also made a downloadable PDF version at:
http://msdn.microsoft.com/library/d...ml/scalenet.asp
This has a good number of well-organized do's and dont's that would let
you dig through and check to see if there is something going on in your
code that could be altered or some setting that could be tweaked to avoid
your issues.
>
>
--
Hope this helps,
Mark Fitzpatrick
Former Microsoft FrontPage MVP 199?-2006
>
"Sachin Salgarkar" <sachin@.aegiscommerce.comwrote in message
news:uN7rUpG7GHA.4552@.TK2MSFTNGP05.phx.gbl...

Quote:

Originally Posted by

>We have a Win 2003 Server that runs around 15 instances of an ASP.NET 1.1
>Web Application ( in the same application Pool).
>Each instance connects to a SQL 2K database on a separate database
>server.
>The database size is around 100 MB (min ) to 3 GB Max.
>The web server is a 2.6 GHZ Xeon with 2 GB of RAM.
>The database server is a dual proc Xeon with 4 GB of Ram.
>Each instance of the Web Application has an average of 15 users.
>>
>We reboot the servers every weekend.
>I have set the Worker Process to recycle at 4 AM everyday.
>>
>The problem is that our clients often receive Out Of Memory exceptions.
>Task
>Manager doesn't show any abnormal activity.
>The Memory Utilization on the web server seems to be around 500 MB ..
>which
>should be fine for a 2 GB RAM system that is used solely as a web server.
>My questions:
>1 Are we overloading the server. ?
>2 What tweaks or configuration changes can we do to improve performance.
>>
>Thanks,
>Sachin Salgarkar
>>

>
>

web service error

hi all,
my web service runs on my machine with IIS. however it gives the error below when i put the web service on the net. what s the problem, can anyone tell me plz. thanks.

Server Error in '/' Application.

---

Runtime Error

Description:An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File --><configuration> <system.web> <customErrors mode="Off"/> </system.web></configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File --><configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web></configuration>

it is better to post this in Web servicecs forum to get better reply

i upload the web service in a folder with same address of the webforms which will consume it. so what is missing?

web service runs after calling ASPX page is closed

I have been racking my brain trying to figure this one out, so any ideas would be appreciated!!

I have been working on a web service. From the web service call, queries are executed and update sql's are executed. The test aspx page that calls the web service is just looping through a ton of records and calling the web service in a loop over and over. When I close the web page, the web service is obviously still running because I can open up Sql Profiler for Sql Server 2000 and see queries still getting launced. I can use Query Analyzer to see the number of non null values for a field in the table that gets updated and it keeps going down (and since the update sql from the web service is setting this field to a non null value, it must still be running).

Is this normal or am I missing something? Is there a way to control this? I'm worried about our application going into production and many users abandoning their browser session yet the web service and sql server keep on working eating up valuable resources.

Thanks for any thoughts and I can post code if that would help.This is normal behavior.

Inside the ASPX page, you can check to see if the client is still connected with Response.IsClientConnected.

Be very careful, however, because on IIS 5.0 this check needs to make an out of process call, which could end up hurting performance. You'll need to do some measurements of your application.

Web Service under other process

Can I create a web service that runs under something other than
aspnet_ws.exe? I would like to create my own process because when it
runs it needs a lot of memory but when it's done it can die.
Thank youIn IIS 6 you can run it in a separate application pool (it's still the
same process though).
What do you mean by "when it's done it can die"?
You can set up Remoting, instead, and have it listen to port 80 (provided
there is no web server on the box). It is a bit more involved on your end,
but the process can "die" once finished, other than the listener.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Antonio" wrote:

> Can I create a web service that runs under something other than
> aspnet_ws.exe? I would like to create my own process because when it
> runs it needs a lot of memory but when it's done it can die.
> Thank you
>
Even if you run it inside a different process it will require just as
much memory.
Are you using IIS 6.0? You can set the worker process to terminate
after a period of idle activity.
Scott
http://www.OdeToCode.com/blogs/scott/
On 8 Aug 2005 06:43:01 -0700, "Antonio" <blarfoc@.yahoo.com> wrote:

>Can I create a web service that runs under something other than
>aspnet_ws.exe? I would like to create my own process because when it
>runs it needs a lot of memory but when it's done it can die.
>Thank you
sure. create a commandline utility in .net, then have the webservice spawn
it. use stdin/stdout for communication.
-- bruce (sqlwork.com)
"Antonio" <blarfoc@.yahoo.com> wrote in message
news:1123508581.235810.188120@.g14g2000cwa.googlegroups.com...
> Can I create a web service that runs under something other than
> aspnet_ws.exe? I would like to create my own process because when it
> runs it needs a lot of memory but when it's done it can die.
> Thank you
>
sorry for not saying, the server is Win2000 server running IIS5.

Web Service under other process

Can I create a web service that runs under something other than
aspnet_ws.exe? I would like to create my own process because when it
runs it needs a lot of memory but when it's done it can die.

Thank youIn IIS 6 you can run it in a separate application pool (it's still the
same process though).

What do you mean by "when it's done it can die"?
You can set up Remoting, instead, and have it listen to port 80 (provided
there is no web server on the box). It is a bit more involved on your end,
but the process can "die" once finished, other than the listener.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

"Antonio" wrote:

> Can I create a web service that runs under something other than
> aspnet_ws.exe? I would like to create my own process because when it
> runs it needs a lot of memory but when it's done it can die.
> Thank you
>
Even if you run it inside a different process it will require just as
much memory.

Are you using IIS 6.0? You can set the worker process to terminate
after a period of idle activity.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On 8 Aug 2005 06:43:01 -0700, "Antonio" <blarfoc@.yahoo.com> wrote:

>Can I create a web service that runs under something other than
>aspnet_ws.exe? I would like to create my own process because when it
>runs it needs a lot of memory but when it's done it can die.
>Thank you
sure. create a commandline utility in .net, then have the webservice spawn
it. use stdin/stdout for communication.

-- bruce (sqlwork.com)

"Antonio" <blarfoc@.yahoo.com> wrote in message
news:1123508581.235810.188120@.g14g2000cwa.googlegr oups.com...
> Can I create a web service that runs under something other than
> aspnet_ws.exe? I would like to create my own process because when it
> runs it needs a lot of memory but when it's done it can die.
> Thank you
sorry for not saying, the server is Win2000 server running IIS5.