Skip to end of banner
Go to start of banner

Investigate mod-pubsub Multi-node behavior report IN PROGRESS

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »



Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.




Overview

The purpose of this test set is to compare different runs of CheckIn-CheckOut workflow test with different set of mod-pubsub. As we find - to enable multi node on mod-pubsub is needed to change NUMBER_OF_PARTITIONS value to bigger one. In test set we comparing different numbers of nodes and partitions. 


Summary

Test set shows that optimal configuration is 2 containers with 2 KAFKA NUMBER_OF_PARTITIONS. 3 containers with 2 nodes shows higher response times than even one container with one partition. (same for 3 nodes with 3 partitions).


Version

mod-pubsub:1.3.3


Tests


Test#Virtual UsersDurationmod-pubsub setup
1202 hours2 container 1 partition
2202 hours2 containers 2 partitions
3202 hours3 container 2 partitions
4202 hours3 containers 3 partitions

Results comparison

For comparison purposes we'll use Check-In controller and Check-Out controller (summaries all calls) instead of using all calls list.

1 and 22 and 33 and 1

50th pct75th pct
2 and 350th pct75th pct
3 and 150th pct75th pct
Check-In Controller-0.254-0.345-31%Check-In Controller0.410.50243%Check-In Controller-0.066-0.04613%
Check-Out Controller-0.717-0.743-30%Check-Out Controller1.1371.17146%Check-Out Controller-2.859-7.34716%


CPU comparison during tests

Test 1:   2 containers,  1 partition

Node 1:

Node 2:


Test 2:   2 containers,  2 partitions

node 1:

node 2:


Test 3:  3 containers, 2 partitions

node 1:

node 2:




Test 4:  3 containers, 3 partitions

node 1

node 2

node 3


  • No labels