from a pracitcal perspective, chances are at any given time there will only be 1
person submitting the completed form. 400 seems like a very low number to me.
Now if you're talking about a survey that is sent out to 10K people with a window of 5
hours to submit it, it probably won't be a problem. Most people ignore surveys to
begin with. Unless you know the users absolutely will fill it out, I wouldn't really
worry about it.
sql server 2K is ok as long as you don't have more than 50+ concurrent queries. The
reason for that is the sql server worker thread to CPU ratio is:
2 worker thread: 1 cpu
also, the kind of query has a tremendous impact on performance. if you really have to
support a large number of concurrent insert/updates, you're going to have to dig
around the various sql server community sites and use COM+/DAL. Your bottleneck won't
be the webserver. whether you use IIS, resin or tomcat, the database will the
bottleneck.
peter lin
Thomas McDonald <[EMAIL PROTECTED]> wrote:
I'm not sure if this is the right list to post this
quesiton too, but here goes:
I am doing a web survey on Tomcat 5.0.19 hooked to a
SQL Server 2000 backend I am trying to figure out what
sort of hit rate it can take.
I'll send an email to 400 people inviting them to take
the survey. They all won't show up at once (and I
don't necessarily have to invite them all at the same
time--I can spread it out over 3/4 hours), but I don't
know if Tomcat can take the load of say, 50 people
using the site at once.
Any suggestions on how I can figure this out?
__________________________________
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster
http://search.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Do you Yahoo!?
Yahoo! Search - Find what you’re looking for faster.
