Last post Feb 20, 2006 04:39 AM by William Coleman
Feb 13, 2006 03:46 PM|mschmitz|LINK
hope somebody can help me to sort out my small problem.
We are planning to launch a portal-site written in ASP.Net.
My problem is that I do not have any clue how to calculate the hardware for this.
We are talking about up to 1000 users/sessions at the same time.
What do you recommend for
- OS (Windows 2003 Server Web Edition or higher)
do I have to pay attention on licensing for 1000 users?
-SCSI or SATA
Any help is very much appreciated
Feb 15, 2006 07:03 AM|William Coleman|LINK
It really depends on what your ASP.NET application is doing. What functionality will your ASP.NET application have? For example, will it interact with a database? Or will it be reading/writing to files stored on a disk or a network share?
Feb 15, 2006 08:30 AM|mschmitz|LINK
thx for your reply.
The ASP.Net Application should interact with a database, normally SQLServer-2000.
And it should provide a few Webservices ind ASP.NET.
Feb 15, 2006 03:58 PMemail@example.com|LINK
Keep in mind that Server 2003 Web Edition won't run SQL, though it provides a decent front end to a separate SQL server. The IIS Resource Kit has some decent guidelines on performance and provisioning, but there are so many variables that there's no right
answer to this. 1,000 portals where each portal has a single page and each portal gets three hits a week will run on my cell phone. 1,000 portals that are named Yahoo, MSN, Google, Amazon, AOL, etc. won't run on any known single piece of hardware in the
Prototype, benchmark and stress test. Repeat until money is exhausted. :)
Feb 15, 2006 05:21 PM|mschmitz|LINK
ok, I see there is no rough rule of thumb.
My Problem is, I have to take the rule of the developer of the portal and it is not developed yet.
I really much like to do it in ASP.Net because I love it, but I don't know how to explain why we should use ASP.NET on a windows. I think my clients/partners will say that it is too expensive to host and for security reasons and performance issues and so on.
I trust in ASP.Net, Windows 2003 and SQL-Server but I dont know how to pitch this to my partners/clients. They will say why don't we use PHP/MYSQL to get it done, just for performance and cost issues.
Feb 15, 2006 11:29 PMfirstname.lastname@example.org|LINK
For one thing, SQL Server way out performs MySQL.
Feb 20, 2006 04:39 AM|William Coleman|LINK
Have you spoken to your clients/partners yet? Perhaps if you give me a list of their concerns and then I can help you to answer them.