Go to home topic Home    Go to parent topic Parent Topic    Go to previous topic Previous    Next Go to next

High backend dataset

Results of additional tests > Effect of DataSource threads on performance > High backend dataset

This test demonstrates how Liberator performs when handling a high rate of updates from the DataSources.
 

<br>
DataSource threads<br>
High backend data set<br>


DataSource threads
High backend data set

 

The graph shows that when there is a very high rate of updates from the DataSource(s), the more DataSource threads running in the Liberator the better.

Test details

Liberator version:

4.4

Number of DataSources
(= number of DataSource threads in Liberator):

1 3

Number of Liberator session threads configured:

1

Number of Clients:

From 40 to about 850

Number of DataSource objects available:

100,000 objects

Each client subscribes (at random) to:

200 objects

Update rate on each object subscribed to:

1 update/sec

Message Content for each update:

5 fields:
One field of 13 characters (timestamp)
Four fields of 3 characters each
Total 25 bytes of update data
Total message size: 50 bytes.

Bytes/second delivered to each client:

10,000 bytes/sec

Liberator burst-max Setting:

0.1



Go to home topic Home    Go to parent topic Parent Topic    Go to previous topic Previous    Next Go to next