Number Of Threads Per Client - HP ML570 - ProLiant - G2 Tuning Manual

Novell NetWare 6 performance tuning guidelines for ProLiant servers
number of threads
per client
figure 12. tuning compared to default installation
Effects of Tuning on WebBench NSAPI Test
18,000
16,000
14,000
12,000
10,000
8,000
6,000
4,000
2,000
0
1 4 8 12
Results: With a workload of 60 clients, the ProLiant ML570 G2 server serviced on
average 361% more requests when tuned compared to the results of the out-of-the-box
(default) installation. The significant difference in performance is also due to the fact by
default; logging is enabled whereas during tuning, it is disabled.
One of the methods of increasing the workload stress on your server is by increasing the
number of threads per client. That way the server can be saturated potentially faster with
fewer numbers of clients. This exercise should, however, be done with caution in order to
avoid negative effects on the clients due to insufficient client resources.
Figure 13 shows the performance effects of running 1 thread over 5 threads per client.
figure 13. performance effects of number of threads per client
Effects of Increasing the Number of Threads on WebBench Test
18,000
16,000
14,000
12,000
10,000
8,000
6,000
4,000
2,000
0
1 4 8
Results: With a workload of 60 clients, the ProLiant ML570 G2 server serviced 17%
more requests on average with five threads per client compared to the single thread per
client test mix.
(Higher is Better)
16 20 24 28 32 36
# of Clients
(Higer is Better)
12 16 20 24 28 32 36
# of Clients
40 44 48 52 56 60
40 44 48 52 56 60
Default
Tuned
1 Thread
5 Threads
42