summaryrefslogtreecommitdiff
path: root/TAO
diff options
context:
space:
mode:
authorcoryan <coryan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2002-01-28 20:48:57 +0000
committercoryan <coryan@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2002-01-28 20:48:57 +0000
commit7f23bbd975eaab4ccd387162eebdc17b1d2e0a5b (patch)
tree1cd2d1859be2363bfca9be803010edc27b883865 /TAO
parent34e7a8fd60ba21391abc7a71b417c1970950d1e5 (diff)
downloadATCD-7f23bbd975eaab4ccd387162eebdc17b1d2e0a5b.tar.gz
ChangeLogTag:Mon Jan 28 12:39:50 2002 Carlos O'Ryan <coryan@uci.edu>
Diffstat (limited to 'TAO')
-rw-r--r--TAO/orbsvcs/tests/EC_Throughput/README17
1 files changed, 12 insertions, 5 deletions
diff --git a/TAO/orbsvcs/tests/EC_Throughput/README b/TAO/orbsvcs/tests/EC_Throughput/README
index d3a539cb14d..1ff4896f5c9 100644
--- a/TAO/orbsvcs/tests/EC_Throughput/README
+++ b/TAO/orbsvcs/tests/EC_Throughput/README
@@ -1,9 +1,17 @@
# $Id$
- This test tries to stress the Event_Service by sending events
-in bursts, the user can control the size of the events, the size of
-the burst, the number of bursts and the time between the bursts, the
-number of suppliers and the number of consumers.
+ This test can be used to measure the performance of TAO's
+Real-time Event Service. The test can be configured to change:
+
+1) The number of suppliers connected to the event service.
+2) The number of consumers connected to the event service.
+3) The types of events generated by the suppliers and the consumer
+ subscriptions.
+4) The event payload size.
+5) The number of events generated.
+6) Events are sent in "burst", i.e. a number of events is
+ generated without any pacing, the user can prescribe the number of
+ events in each burst as well as the period between bursts.
There are two versions of the test, a collocated version,
contained in the ECT_Throughput executable. The non-collocated
@@ -11,7 +19,6 @@ version uses the event channel executable in the ../../Event_Service
direction, and two local binaries (ECT_Consumer and
ECT_Supplier). Both versions require a Naming Service.
-
To run the test you can use (as usual) the run_test.pl script
on this directory. If you want to manually run the tests here are
some examples, usually each one of the commands below is executed on