Jira Legacy |
---|
server | System JiraJIRA |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | MSEARCH-300 |
---|
|
...
Test with long ramp-up period, 1 minute per user from 0 to 25 users
Environment
- mod-search 1.6.4
- OpenSearch service
- kafka 2.8.0
Summary
- ALL tests (1-50 users) ended without errors. Average response time . most resource intensive is mod-search. During test 50 users call number browsing CPU usage reached more than 300%.
- During tests 50 users with background activities (CICO+ Data Import) response time increased up to 10%-15%.
number of users | average rt | % CPU mod-search |
---|
1 | 0.148 | 12 |
5 | 0.168 | 42 |
10 | 0.191 | 75 |
20 | 0.321 | 122 |
50 | 1.821 | 158 |
1 user
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 1747 | 1747 | 0 | 0 | 2.220 | 0.053 | 0.142 | 0.166 | 0.255 | 0.308 | 0.687 | 0.148 | 0.251 |
5 users
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 8219 | 8219 | 0 | 0 | 10.693 | 0.048 | 0.150 | 0.188 | 0.295 | 0.419 | 0.920 | 0.168 | 0.292 |
10 users
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 12741 | 12741 | 0 | 0 | 20.313 | 0.051 | 0.161 | 0.233 | 0.387 | 0.584 | 1.437 | 0.191 | 0.384 |
20 users
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 12193 | 12193 | 0 | 0 | 32.169 | 0.052 | 0.245 | 0.441 | 0.739 | 1.025 | 2.441 | 0.321 | 0.736 |
50 users
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 7849 | 7849 | 0 | 0 | 38.485 | 0.081 | 0.963 | 1.259 | 1.823 | 2.182 | 3.275 | 0.996 | 1.821 |
50 users 30 min (10 min ramp up)
...
Call number browsing with background CICO activity.
A large usege usage of processor resources is observed in the mod-search module during call number browsing. I guess need to increase the processor resources in tack task definition of this module.
...
Call number browsing + DI + CICO
Call number browsing with old cluster
1 user
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 2643 | 2643 | 0 | 0 | 2.233 | 0.044 | 0.125 | 0.164 | 0.285 | 0.494 | 0.948 | 0.145 | 0.278 |
10 users
Image Added
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 25569 | 25569 | 0 | 0 | 21.363 | 0.043 | 0.138 | 0.194 | 0.350 | 0.611 | 1.937 | 0.167 | 0.346 |
20 users
Image Added
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 41155 | 41155 | 0 | 0 | 35.026 | 0.041 | 0.196 | 0.355 | 0.671 | 1.078 | 2.625 | 0.271 | 0.669 |
50 users
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 103398 | 103398 | 0 | 0 | 89.437 | 0.041 | 0.211 | 0.313 | 0.534 | 0.896 | 2.146 | 0.251 | 0.530 |
Image Added
100 users
Requests | Total | OK | KO | % KO | Req/s | Min | 50th pct | 75th pct | 95th pct | 99th pct | Max | Average | Latency |
---|
GET_browse _call_numbers | 106865 | 106865 | 0 | 0 | 93.836 | 0.044 | 0.727 | 0.978 | 1.394 | 2.073 | 4.713 | 0.758 | 1.389 |
Image Added
users | new cluster | old cluster |
---|
1 | 0.148 | 0.145 |
10 | 0.191 | 0.167 |
20 | 0.321 | 0.271 |
50 | 1.821 | 0.251 |