3 This test can be used to measure the performance of TAO's
4 Real-time Event Service. The test can be configured to change:
6 1) The number of suppliers connected to the event service.
7 2) The number of consumers connected to the event service.
8 3) The types of events generated by the suppliers and the consumer
10 4) The event payload size.
11 5) The number of events generated.
12 6) Events are sent in "burst", i.e. a number of events is
13 generated without any pacing, the user can prescribe the number of
14 events in each burst as well as the period between bursts.
16 There are two versions of the test, a collocated version,
17 contained in the ECT_Throughput executable. The non-collocated
18 version uses the event channel executable in the ../../Event_Service
19 direction, and two local binaries (ECT_Consumer and
20 ECT_Supplier). Both versions require a Naming Service.
22 To run the test you can use (as usual) the run_test.pl script
23 on this directory. If you want to manually run the tests here are
24 some examples, usually each one of the commands below is executed on
27 # Run the collocated test using the default configuration:
28 $ ../../Naming_Service/Naming_Service
31 # Run the non-collocated test using the default configuration:
32 $ ../../Naming_Service/Naming_Service
33 $ ../../Event_Service/Event_Service
37 # Run the non-collocated tests using 4 suppliers, notice that the
38 # ECT_Consumer needs to know the number of suppliers to terminate
40 $ ../../Naming_Service/Naming_Service
41 $ ../../Event_Service/Event_Service
45 Other options for the tests can be obtained using the -?, for
48 # Find out the options for the collocated test: