How many users can a .net server handle?

[Tom]

how many user connections can a .net server connecting to a sql2000
server, handle before degradation takes place. What is the general
rule of thumb, given a Dual P4 2Ghz Ultra 160 SCSI .net server with
2GB Ram?

[Jerry III]

There isn't any. It all depends on what type of requests and what exactly
does each request do. The number can be from a request per couple seconds
(if you really don't know what you're doing) to thousands requests per
second.

Jerry

"Tom" <root@127.0.0.1> wrote in message
news:7lkoivk21ukj5b9h5icf2l5gto3q8fg3e0@4ax.com...

> how many user connections can a .net server connecting to a sql2000
> server, handle before degradation takes place. What is the general
> rule of thumb, given a Dual P4 2Ghz Ultra 160 SCSI .net server with
> 2GB Ram?
>

[Yan-Hong Huang[MSFT]]

Hello Tom,

Thanks for posting here.

Jerry and Natte are right. The performance depends on the architectureof your web application, such as how it uses data
access, how to transaction, and etc. The best way to judge whether your system could afford it is to test it by using
Application Center Test. In the test, we could identify the bottleneck of the performance and improve it.

You could also get idea from these articles:
"Performance Comparison: Data Access Techniques"
[url]http://msdn.microsoft.com/library/en-us/dnbda/html/bdadotnetarch031.asp?frame=true[/url]

"Developing High-Performance ASP.NET Applications"
[url]http://msdn.microsoft.com/library/en-us/cpguide/html/cpcondevelopinghigh-performanceaspnetapplications.asp?[/url]
frame=true

HTH.

Best regards,
Yanhong Huang
Microsoft Online Partner Support

Get Secure! - [url]www.microsoft.com/security[/url]
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
!From: "Jerry III" <jerryiii@hotmail.com>
!References: <7lkoivk21ukj5b9h5icf2l5gto3q8fg3e0@4ax.com>
!Subject: Re: How many users can a .net server handle?
!Date: Sat, 2 Aug 2003 20:51:37 -0700
!Lines: 16
!X-Priority: 3
!X-MSMail-Priority: Normal
!X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
!X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
!Message-ID: <e$yUKKXWDHA.2284@TK2MSFTNGP10.phx.gbl>
!Newsgroups: microsoft.public.dotnet.framework.aspnet
!NNTP-Posting-Host: h-69-3-117-40.lsanca54.covad.net 69.3.117.40
!Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
!Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:164382
!X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
!
!There isn't any. It all depends on what type of requests and what exactly
!does each request do. The number can be from a request per couple seconds
!(if you really don't know what you're doing) to thousands requests per
!second.
!
!Jerry
!
!"Tom" <root@127.0.0.1> wrote in message
!news:7lkoivk21ukj5b9h5icf2l5gto3q8fg3e0@4ax.com.. .
!> how many user connections can a .net server connecting to a sql2000
!> server, handle before degradation takes place. What is the general
!> rule of thumb, given a Dual P4 2Ghz Ultra 160 SCSI .net server with
!> 2GB Ram?
!>
!
!
!