rafaelc
Jun 5th, 2001, 11:24 AM
I was wondering if anyone could explain this one.
I'm doing WAS testing with ASP and MTS.
I've got an ASP page that calls one MTS component. (one-to-one relationship).
IIS 4.0 by default is configured to run 10 worker threads per processor on a box.
I'm working on a quad, so I could have 40 concurrent ASP page
requests running at any given time.
When I do a test with 100 simultaneous users I see 40 requests executing and 60 queued in performance monitor (makes sense).
Now, when I view the components in MTS explorer (at the same time) I see more that 40 (about 50-56) objects spinning.
If I could only have 40 requests executing in IIS at one time.... How can I have more than 40 objects running in an MTS package if there is a one-to-one relationship here?
I appreciate the feedback.
bv
I'm doing WAS testing with ASP and MTS.
I've got an ASP page that calls one MTS component. (one-to-one relationship).
IIS 4.0 by default is configured to run 10 worker threads per processor on a box.
I'm working on a quad, so I could have 40 concurrent ASP page
requests running at any given time.
When I do a test with 100 simultaneous users I see 40 requests executing and 60 queued in performance monitor (makes sense).
Now, when I view the components in MTS explorer (at the same time) I see more that 40 (about 50-56) objects spinning.
If I could only have 40 requests executing in IIS at one time.... How can I have more than 40 objects running in an MTS package if there is a one-to-one relationship here?
I appreciate the feedback.
bv