I would try sql server forums first to see what kind of load your server can handle. You can load test some sample queries using JMeter. this will tell you the upper limit for your particular server. [EMAIL PROTECTED] - if you have questions. If you're using a single CPU server, you should be able to handle 10 active sessions without any problems. assuming you've taken care to write stored procedures and you're not doing funky joins. Reads won't be any problem for you, it's really the writes. peter lin
Thomas McDonald <[EMAIL PROTECTED]> wrote: Thanks. Actually all the people will take it. It is an internal survey and they are being told by their managers that they must take it. That said, I would expect about 12-25 people hiting the site at any one time (If I send out all 400 invitations at one time). Also, it isn't a one shot survey submission. It is a 3-4 question at a time kind of survey and about 200-300 questions total. So there will be lots of reads/writes. Some of the initial queries are complex (lots of joins, etc.) so I am a little worried about SQL performance. Anyway, I'll take this to the the list mentioned by J.Petersen: [EMAIL PROTECTED], but if anyone has anymore useful comments I would welcome them. --- Peter Lin wrote: > > 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 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. __________________________________ 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.
