Oracle Audio Technologies A86828-01 User Manual
Page 34
Understanding Concurrent Users and User Population
3-2
Oracle HTTP Server powered by Apache Performance Guide
relationship between the number of potential users and the number of concurrent
users. This is determined by the think time and the average response time for your
application.
To determine memory requirements, you also need to consider the number of
concurrent executing users (not the total user population) times the cost per user.
provides an example of the impact of think time and service time on the
concurrency and resulting performance of a system.
Note:
The MaxClients setting in your httpd.conf file limits the
number of concurrently executing users. See
page 4-9 for information on the MaxClients directive.
Table 3–1
Concurrent executing users
User
population
1
1
User population - total users.
Think
time
(sec)
2
2
Think time - the time the user is not engaged in actual use of the processor (the time between
requests).
Service
time
(sec)
3
3
Service time (seconds) - elapsed time to complete the operation measured for a single user.
Range of
concurrent
users
4
4
Range of concurrent users - the number of users measured on the server, taken in snapshots from the
server-status display (requests currently being processed). See
"Using the mod_status Utility"
page 3-3 for information on server-status.
Average
response
Time
(sec)
5
5
Average response time - response time measured at the client under load.
Requests per
second
(throughput)
6
6
Requests per second (throughput) - number of requests processed.
CPU
utilization
(%)
7
7
CPU utilization - average total CPU utilization as a percentage.
100
0
0.3
100
5.2
19
99
100
1
0.3
65-100
4.2
19
99
100
10
0.3
0-32
0.9
9
48
100
10
0.6
0-53
2.9
8
80