README
1Perf Test Suite
2============================================
3
4The perf tests has to be run as two different processes -
5a perf server and a perf client. The perf server need to be started
6before a perf client process can be invoked.
7
8Various RPC request combinations can be tested as input to
9perf client process.
10
11The following scripts are provided to execute a minimal set
12of perf tests:
13 run_client.sh (can be run with both tcp and udp).
14 perf_udp.sh
15 perf_tcp.sh
16
17Usage of these scripts:
18run_client.sh `string binding returned by server`
19perf_udp.sh server_host_name client_program_directory
20perf_tcp.sh server_host_name client_program_directory
21
22Before executing any of these scripts, a server need to started
23with appropriate protseq_spec.
24
25An example run of these scripts involve starting the server:
26
27 ./server 1 ncadg_ip_udp
28 ==> returns binding, such as ncadg_ip_udp:130.105.4.102[2001]
29 run_client.sh 'ncadg_ip_udp:130.105.4.102[2001]'
30 perf_udp.sh server_host_name .
31or
32 ./server 1 ncacn_ip_tcp
33 ==> returns binding, such as ncacn_ip_tcp:130.105.4.102[2001]
34 run_client.sh 'ncacn_ip_tcp:130.105.4.102[2001]'
35 perf_tcp.sh server_host_name .
36
37The alternate methods of executing the perf tests are provided
38in the DCE Porting and Testing Guide.
39