Reasonable Number of Max Users

R

RAK

I have an application that uses asp DNS-less connections to either ACCESS
databases or sql databases depending on where the data is stored.

In the past, I have found that the response to 20-25 simultaneous users are
essentially the same whether the connection is to ACCESS to sql. The
application requires the database to serve up relatively small bits of
information -- a couple sentences of text or a description of a link to
another file. (This is a classroom test management system that services up
problems to students etc.)

This past semester, I got a little complacent about which database to use.
Decision was made on which was going to be "more permanent" etc.

This leads to my point. This past final exam period I have some ACCESS
databases attempting to serve up problems to 50-70 students at some of the
final exam periods. The ACCESS database has locked up in the middle. It
application (active server pages through a win2k3 server with IIS 6.0)

What intriges me why it seems to just freeze the application rather than
just degrading to a gradual standstill.

I don't have any tools for any kind of stress testing. So any thoughts on
why I have experienced abrupt freeze vs. gradual degrading would be of
interest me.

To all those who have taken the time to read this. Thanks.
R. Kuntz -- Monmouth University
 
Top