| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | PERF-152 |
|---|
|
...
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).
Partitioning logic depends on event types. It means that with "one call test" in any case we'll use only one partition of mod-pubsub. As for CheckIn-CheckOut test we might use one partition more than other (or other two) that can explain differences in CPU usages on different nodes. So bigger partition number can help with complex workflows or with real users.
Version
mod-pubsub:1.3.3
Tests
...
For comparison purposes we'll use Checkformula to summarize Check-In controller and Check-Out controller (summaries all calls) , instead of using all calls list.
and and and 1| vs 1 | 4 vs 3 |
| 50th pct | 75th pct | 75 % difference | 50th pct | 75th pct |
2 and 3| 75 % difference | 50th pct | 75th pct |
3 and 1| 75 % difference | 50th pct | 75th pct | 75 % difference |
| Total Check- |
In Controller.254.34531%CheckIn Controller0.41 | 0.502 | 43% | Check-In Controller | -0.066 | -0.046 | 13% | Check-Out Controller | -0.717 | -0.743 | -30% | Check-Out Controller | 1.137 | 1.171 | 46% | Check-Out Controller | -2.859 | -7.347 | 16%| 0,222 | -0,172 | -33% | -0,671 | -0,862 | -137% | 2,416 | 3,018 | 341% |
| Total Check-out | 3,188 | 4,112 | 120% | 1,763 | 2,079 | 40% | 4,951 | 6,191 | 169% | -7,451 | -9,506 | -475% |
CPU comparison during tests
Test 1: 2 containers, 1 partition
...