Infrastructure

[Guest]

Im not sure if this is the correct newsgroup so please feel free to directo
me to a more appropriate group.

I designing a system that will be developed using ASP.Net 1.1 and will have
a SQL Server 2000 backend. The system will be used by 200 users with
probably only 100 ever using at any one time.

The idea is to have a dedicated web server which will double up as an
application server. I was intending to use an existing SQL Server box bor
the backend.

I have very little knowledge of hardware capabilities so Im wondering if
this setup would be acceptable or if I would need a seperate application
server & a dedicated sql server.

How do I measure how much hardware I need to satisfy my software requirements?

Terry Holland

 

[Cor Ligthert [MVP]]

Terry,

In my opinion is this not a question for a newsgroup, you can get a lot of
good meant advices, however as well are important.

The backbone that you use
Your connection to that backbone
The type of servers you use
The type of disks you use
The available memoyr
The available processors.
The other or not other load on those servers
Etc. etc.

I think that this can never be given in a newsgroup.

Sorry just my opinion.

Cor

 

[Guest]

Terry,

Cor's right in saying that's hard to answer. That's a general question with
a lot of variables that affect the requirements.

You could design a web app that would support 1,000 users with ease or get
bogged down with 10. And the difference may be as simple as a few indexes in
your SQL Server database.

I think you gain a lot of this type of knowledge by failing (or coming
close) a few times. I don't think an app that supports 200 users would be one
that you would want to fail at.

If you already have servers, I would suggest starting with a small subset of
the system and working up to complete functionality over time. With a little
bit of performance monitoring, you will be able to build your knowledge
rapidly and not affect as many application users.

-Mike S.

 

[Chris Mullins]

I designing a system that will be developed using ASP.Net 1.1 and will
have
a SQL Server 2000 backend. The system will be used by 200 users with
probably only 100 ever using at any one time.

The idea is to have a dedicated web server which will double up as an
application server. I was intending to use an existing SQL Server box bor
the backend.

How do I measure how much hardware I need to satisfy my
software requirements?

The short answer is:
You'll probably be fine. Your user loads are so light, and modern hardware
is so fast, that you shouldn't have anything to worry about. Unless you're
doing something strange, performance shouldn't be an issue. If this app is
used internally, and the web server is hosted inside your LAN, you're
probably even ok from a basic security perspective.

The long answer: It depends. There are all kinds of screwy reasons
performance could be a problem - RAM , transactions, sql locks, reporting
criteria, unique resources, etc. There are also all sorts of reasons a
physical seperation between your web server and your application server is a
better choice, and then throw your Sql Server into an Sql Dmz - especially
if your front end is exposed on the Internet. It all depends on
requirements.

 

[Guest]

Thanks for all responses. I will go with a dedicated web server which will
double up as an application server and existing SQL Server box for the
backend.

I will then open app up to users gradually to monitor performance

Terry Holland

 

[abukase1]

tes