don't know if I'd be able to help too much. But, I do have a few insights on the simultaneous users.
We recently had a dispute with a client over what was meant by "concurrent users". The nature of the web environment allows concurrent users, with little problems. However, the client did not specify he meant "concurrent database updates", which is slightly different. End result was that we had to revise our updates to handle database concurrency (only took a couple of days). But, the original app DID in fact meet the requirement of "concurrent users", as multiple users could use the app at the same time. So, my suggestion is to get a VERY clear idea of what is meant by "simultaneous users". Do they mean 250 people using the app at any given time? or 250 database updates at precisely the same instant? Either way, it comes down to how the code is written. My own performance testing indicates our test server was able to handle 1.3 million users per hour. But this was a very simplistic test meant solely to compare numbers with another system doing the same sort of work. (.Net server vs CF server - results were somewhat inconclusive) If you only need to allow 250 users access to the application at any given time, then your job is likely done. IIS and CF can easily handle thousands of hits in a very short time frame. As for simultaneous requests option, the likely hood of 250 people requesting information from the server at precisly the same instant is unlikely. You are more likely to see a small subset of this group (10% maybe) making requests at the same instant, in which case, the queue system would handle that fine (as far as I know). That's my two cents worth, but I'd take the advice/suggestions of the more well known gurus over mine. (Maybe Dave Watts has some insight?) HTH Shawn Grover -----Original Message----- From: Dave Carabetta [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 02, 2002 2:03 PM To: CF-Talk Subject: Performance Tuning Metrics Help I am on the verge of finishing an application and I am starting to do some performance testing. One requirement sent to me by the executives is that the app must be able to support "250 simultaneous users" at a time. My question is, what exactly constitutes "250 simultaneous users"? Is that supposed to mean the ability to support 250 people all hitting the submit button at precisely the same time? Or 250 people using the app at a given instance? Can CF realistically support that figure if the answer is "all at one time"? I mean, I guess the phrase is somewhat open to interpretation, but I was just wondering if there was some standard definitions in the performance tuning world that definitively answers what "simultaneous" is meant to be. Also, if I have the number of simultaneous requests set to 3 in my CF administrator, how does CF's queue hold up with 247 requests waiting? As a rule, is it flaky? What happens in a clustered environment (say 2 servers)? I know that's a lot of questions, but I'm trying to work on these skills, as they are as important as being able to write the CF code itself. As you can probably tell, I'm relatively new to detailed performance tuning. If it makes any difference in the answers, I'm using CF 4.5.2 on Solaris with Apache 1.3.6 as my web server. Thanks in advance, Dave. _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
