|
> From: "Brad Stone" <brad@bvstools.com> > Please let us know you're experience details, because > I've noticed exactly the opposite. Unless your apps > are taking over a minute to be processed, the opposite > should be the case. Brad, By using the term "thread" are you thinking that I mean one of the HTTP Server BCI Jobs? That's not what I mean. Although each HTTP Server thread may interface with one BCI Job. To see what I mean, use WRKACTJOB SBS(QHTTPSVR), then key 12 in the input field next to the HTTP Server's BCH Job. That will enable you to work with the HTTP Server threads. If you simultaneously monitor those threads in conjunction with the NETSTAT *CNN screen, while users are hitting the site, it will become clear to you that each user holds a lock on multiple threads during their visit. To further illustrate, use the CHGHTTPA command to set threads to a low value, while attempting to use multiple instances of Internet Explorer to access the site. The site will lock up and the browser will show nothing more than the hour glass pointer. On average, each user needs 2-3 threads. By multiple instances of Internet Explorer, I mean starting a new instance from the desktop, not a new window launched from the currently running instance. It a fairly good way to simulate multiple users. Nathan M. Andelin www.relational-data.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.