Changes between Version 89 and Version 90 of benchmarks

Timestamp:

11/24/11 08:39:00 (12 years ago)

Author:

bartek

Comment:

--

benchmarks

@@ -175 +175 @@
 
 ''Pros:''
-* Possibility to compare performance of the systems in the most basic, but typical scenario.
+* Possibility to compare performance of the systems in the most basic, but typical scenario, where notifications are not forwarded to Notification Consumers.
 * The delay imposed by the notification systems as well as the network may be easily measured by comparison to the times of sending notifications between lightweight Publisher and Notification Consumer programs.
 
@@ -187 +187 @@
 
 === Test 2 - Notification Delivery with Active Subscriptions ===
-In this test the measured value was the time of forwarding notifications from Publisher to Notification Consumer via different systems. In contrast to the previous test, here the tested systems utilized Subscriptions and on their basis determined where to send a certain notification. The next importand difference was the move of the time measurement from Publisher to Notification Consumer.
+In this test the measured value was the time of forwarding notifications from Publisher to Notification Consumer via different systems. In contrast to the previous test, here the tested systems utilized Subscriptions and on their basis determined where to send a certain notification. The next importand difference was the move of the finish time measurement from Publisher to Notification Consumer.
 
 ==== Main facts ====
 * Scenario's draft: Publisher -> Notification Broker -> Notification Consumer
-* Time measurement: on Notification Consumer's side (however the start time still is established by Publisher)
+* Time measurement: on Publisher's side (start time) and on Notification Consumer's side (finish time)
 * Filtering based on: topics
 * Notification dialect: Simple
@@ -197 +197 @@
 * Number of notifications in one bunch: 1000
 
+==== Notes ====
+
+''Pros:''
+* Possibility to compare performance of the systems in the typical scenario with notification forwarding to Notification Consumers.
+* The time is measured not only by Publisher but also by Notification Consumer which gives more precise results of processing time.
+
+''Cons:''
+* The Publisher installed only on a single machine.
+* The notification services in a default configuration and only marginally loaded (only several subscriptions).
+* WebSphere Application Server concatenates received messages if they are forwarded to the same NotificationConsumer - although in general it improves the performance, sometimes it imposes delays.
+
+==== Results ====
+[[Image(test-2.png, center, width=540px)]]
+
+
 === Test 3 - Subscribing ===