ASP.NET performance benchmark

[ke zhang]

Hi,

We are building a portal web site using ASP.NET, the peak number of
users is expected to be around 1 million. Is there good information
about ASP.NET performance benchmark? Is there any recommendation like:
what would be a good size of a page, how large viewstate can be and
how many datagrid controls can be used on a single page and etc, while
ASP.NET is under heavy load?

Greatly appreciated for any comments/suggestions/information!


ke

 

[Robert Wagner]

1 million/sec?
1 million/min?
1 million/day?
1 million/month?
1 million/year?

What kind of servers. You sound vague on what you have?

To give you a rough (ie educated guess) on recommended servers:

1 million/year - Workstation/Server
1 million/month - SCSI Server, Dual CPU, 4GB
1 million/day - "a Real server", ie 8-way, SCSI RAID 1/0, 8GB RAM , or a Sun
1 million/min - Cluster of Real Servers

Anyway I'm offtrack. For 1 mill/year I wouldn't worry much about cutting
down on the size of the the code. You much better off making the code
readable and easy to maintain.

For 1 mill/month, and a _great_ server you may get away with the stratagy
above. Otherwise I'd forgo the datagrid as it is bulky and resource hungry.
I'd go down the path of gettting the stuff myself and writing custom, quick
code. For that kind of deployment you can spend the extra time.

For anything less, I'd seriously consider something other than ASP.NET.
ASP.NET is really resource hungry compared to Perl, PHP, etc. The same can
be said to ASP and JSP to a lesser extent.

On a side note, if your talking about 1mill simultanious or 1mill/min and
you are asking this question, I would seriously get some outside help for
someone who knows what they are doing. No offence, but I would do the same
as I've never done something as crazy (?) as that

Robert

 

[John Timney \(Microsoft MVP\)]

Check out the design patterns and practices site at MS,
http://www.microsoft.com/resources/practices/

specifically the Architect Webcast on Improving .NET Applications
Performance and Scalability that is being held in a week or two, and the
Enterpise pattern
http://msdn.microsoft.com/practices/type/Patterns/Enterprise/default.asp

Howver, sounds to me like you are re-inventing the wheel. Portal server
2003 with the correct architecture should give you the scale you require out
of the box - if I was designing a portal based on asp.net then that would be
my first port of call.

--
Regards

John Timney (Microsoft ASP.NET MVP)
----------------------------------------------
<shameless_author_plug>
Professional .NET for Java Developers with C#
ISBN:1-861007-91-4
Professional Windows Forms
ISBN: 1861005547
Professional JSP 2nd Edition
ISBN: 1861004958
Professional JSP
ISBN: 1861003625
Beginning JSP Web Development
ISBN: 1861002092
</shameless_author_plug>