Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!asuvax!anasaz!qip!john
From: john@qip.UUCP (John Moore)
Newsgroups: comp.benchmarks
Subject: Re: How do maxed out users compare to users with think times
Message-ID: <6660@qip.UUCP>
Date: 14 Jun 91 06:14:02 GMT
References: <4046@sixhub.UUCP> <6648@qip.UUCP> <1991Jun13.215233.11601@csusac.csus.edu>
Organization: Anasazi, Inc.  Phoenix, Az
Lines: 30

In article <1991Jun13.215233.11601@csusac.csus.edu> croft@csusac.csus.edu (Steve Croft) writes:
]>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...

Not in our case:
  (1)the database consumes almost all of the CPU used
  (2)the benchmark uses the entire application
  (3)we run the same number of processes on our system no matter how many
   users there are - our number of processes is more closely related
   to the number of processors.
  (4)the OS we are using (Pyramid's) scales linearly with the number
   of user processes to well beyone 270, so even in the absence of (3),
   we still wouldn't run out of CPU (but we might run out of memory).

Sorry about the confustion.
-- 
John Moore HAM:NJ7E/CAP:T-Bird 381 {ames!ncar!noao!asuvax,mcdphx}!anasaz!john 
USnail: 7525 Clearwater Pkwy, Scottsdale,AZ 85253 anasaz!john@asuvax.eas.asu.edu
Voice: (602) 951-9326        Wishful Thinking: Long palladium, Short Petroleum
Opinion: Support ALL of the bill of rights, INCLUDING the 2nd amendment!
Disclaimer: The opinions expressed here are all my fault, and no one elses.