Costin, See below. >>>>>>>>>>>>>>>>>Original Message <<<<<<<<<<<<<<<<<< On 11/9/00, 2:11:12 PM, [EMAIL PROTECTED] wrote regarding Re: Test hardware != User hardware => applicability problems?: > > criteria on a limited set of requests. So, one more time: What workload > > is Tomcat expected to run, and what will TC thruput and response be > > running that workload on a particular architecture? Or, since TC is free, > > this is up to the user to simply try it and see? > I don't think you can ( or should ) predict what the user will run, but > how much will tomcat add. I disagree with the above. Users are less interested in implementation details, and more interested in rough metrics. If TC is to appeal to CTO's, etc., data are needed on user-perceived performance: that is, the combined effect of the request and TC). Unless the strategy is to let the user decide what fits their situation, which means that TC will be mostly for hobbyists or techies. > It is important to know that at x req/s tomcat is adding > y ms for each request, z ms for an internal dispatch, etc. > ( of course, on average ) >From a developer perspective, I agree with the above. I don't see the user and developer perspectives as entirely incompatible. Roy -- Roy Wilson E-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
