summaryrefslogtreecommitdiff
path: root/TAO/performance-tests/RTCorba/Multiple_Endpoints/Orb_Per_Priority/README
blob: 4fe699a2116f77f5e112c1b2990063d58b40f84a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
// $Id$

This directory contains programs for measuring performance with
the orb per priority scenario (described below).

For each corba priority specified on the command line, server spawns a
thread, in which it creates an ORB, and exports an ior of the object
registered under the poa of that ORB.
Client runs the specified number of threads at specified priorities (see command
line arguments description below), all concurrently invoking
operations on the server object, but through different IORs.  Each
client thread uses an IOR exported by a server thread (i.e., ORB)
running at the same corba priority as itself.

See run-test.pl for a sample run.  (Perl script starts a server, which
has 5 low-priority orbs and one high priority orb, and
then runs a client with 5 low-priority threads and one high-priority thread).

Command Line Arguments
**********************

server

-o <ior_output_file>      Base name of the file where to store IOR of the server.

-t <corba_priority>       Specify a corba priority of a server
                          thread to run.  This option can be used
                          multiple times in order to specify the
                          number of threads in the server and their
                          priorities. Each thread will have its own
                          ORB and will export its own ior.

client

-i <ior>                  IOR of the object to use for invocations.

-n <number of iterations> Number of invocations each thread must
                          perform on the object.

-p <period>               Period with which invocations should be made.

-t <corba_priority>       Specify a corba priority of a a client
                          thread to run.  This option can be used
                          multiple times in order to specify the
                          number of threads in the client and their
                          priorities.  Each thread will use the ior
                          created by the server ORB of corresponding
                          priority.