Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!csus.edu!ucdavis!csusac!croft
From: croft@csusac.csus.edu (Steve Croft)
Newsgroups: comp.benchmarks
Subject: Re: How do maxed out users compare to users with think times
Message-ID: <1991Jun13.215233.11601@csusac.csus.edu>
Date: 13 Jun 91 21:52:33 GMT
References: <676640053.AA19240@flaccid> <4046@sixhub.UUCP> <6648@qip.UUCP>
Organization: California State University, Sacramento
Lines: 22

In article <6648@qip.UUCP> john@qip.UUCP (John Moore) writes:
>We have been doing extensive benchmarking to predict hotel reservation system
>behavior. Our approach is as follows:
>  -run the benchmarks with simulated "maxed out users." Measure the
>   transaction rate that is sustainable with acceptable response time.
>  -observe real users and measure their "think time"
>  -ratio to determine numbers of users we can support
>
>Typical numbers for one configuration:
>  -max TPS: 10
>  -think time per user 27 seconds
>  -equivalent max number of users 270

There should be a clarification about these numbers; the 270 would
indicate the number of users the database engine can handle.  It
does not mean you could actually run 270 people since that could exhaust
compute resources.  In other words, it might be harder for the
OS to support 270 user applications than it is for the database
engine to handle 270 transactions every 27 seconds...

Steve Croft
stevec@water.ca.gov