One user using one browser generates *ONE* page request; the number of
images on the page may make up another n transactions (where n could be any
number), but these go against the web server, not the webobjects adapter.
I'm curious... Does WebObjects count the retrieval of an image as a
transaction? If so, this would be a good incentive to use images that are
served up by the web server and not processed by webobjects.
I have personally not run into the 25 TPM limit, except when trying to.
>One user using one browser typically creates multiple simultaneous HTTP
>transactions to the server. Netscape Navigator, for example, is by default
>set to make 4 simultaneous transactions each time the user interacts with
>the server. As such, if a user makes 5 request to the server per minute
>(which is a very reasonable and conservative amount) that translates to 20
>tpm from WebObject's point of view. This means that 5 simulataneous users
>will generate 100 transactions per minute. This has been confirmed by our
>developers. They are constantly hitting the 25 tpm limit of the developer
>version even with just one user.
>
-- randy
