Achieving Maximum Throughput with Web Services and ASP.NET Front End?

[Spam Catcher]

Hi all,

I'm building a multi-tier web application that is primarily driven by a web
service back end.

Are there any configuration settings I should know about to increase the
performance of the site?

For example, if the site is going to service 100+ users, do I need to do
anything special to ensure IIS can contact my back-end webservice at the
highest possible throughput?

The webservice will be hosted on the same machine as the website.

The webserivce primarily interacts with a SQL Server database. DTOs are
passed back and forth between the web service and the web front-end
(ASP.NET web application).

Any hints, tips, etc. would be greatly appreciated.

Thanks!

[=?Utf-8?B?Sm9obiBIdW50ZXI=?=]

You may want to check the maxConnections setting. By default .NET restricts
the number of concurrent connections to 2 if you web site is making multiple
web service calls then some of the calls may be queued.

See http://msdn2.microsoft.com/en-us/library/5w91x7a7.aspx for more
informatiom and how to change these settings.

"Spam Catcher" wrote:

Hi all,

I'm building a multi-tier web application that is primarily driven by a web
service back end.

Are there any configuration settings I should know about to increase the
performance of the site?

For example, if the site is going to service 100+ users, do I need to do
anything special to ensure IIS can contact my back-end webservice at the
highest possible throughput?

The webservice will be hosted on the same machine as the website.

The webserivce primarily interacts with a SQL Server database. DTOs are
passed back and forth between the web service and the web front-end
(ASP.NET web application).

Any hints, tips, etc. would be greatly appreciated.

Thanks!

[Spam Catcher]

=?Utf-8?B?Sm9obiBIdW50ZXI=?= <Jo********@discussions.microsoft.com>
wrote in news:2E**********************************@microsof t.com:

You may want to check the maxConnections setting. By default .NET
restricts the number of concurrent connections to 2 if you web site is
making multiple web service calls then some of the calls may be
queued.

See http://msdn2.microsoft.com/en-us/library/5w91x7a7.aspx for more
informatiom and how to change these settings.

I think this was changed in the ASP.NET 2.0 to use the optimal/automatic
configuration (threads, connections, etc are all automatically set to the
maximum number based on CPU).

So besides these settings are there anything else I need to worry about?

Any sort of IIS settings?