Browse/subjects report [Lotus]
- 1 Overview
- 2 Summary
- 3 Environment
- 4 Test Results
- 4.1 Test 1 user
- 4.1.1 Resources usage
- 4.2 Test 5 users
- 4.2.1 Resources usage
- 4.3 Test 10 users
- 4.3.1 Resources usage
- 4.4 Test 1-100 users (Ramp-Up)
- 4.4.1 Resources usage
- 4.4.2 Test 5 users + CICO
- 4.1 Test 1 user
- 5 Test Results openSearch cluster Elasticsearch 7.10
- 5.1 Test 1 user
- 5.1.1 Resources usage
- 5.2 Test 5 users
- 5.2.1 Resources usage
- 5.1 Test 1 user
Overview
The purpose of this test set is to test browse/subject/instances API. Measure performance, find possible issues, bottlenecks.
Summary
1 user test ended without errors. Average response time 5.509 s. Resources usage is hardly visible on mod-search during test (most of work were done on OpenSearch end). OpenSearch CPU usage reached 70%.
5 users test ended without errors. Average response time 7.918s. Resources usage is hardly visible on mod-search during test (most of work were done on OpenSearch end). OpenSearch CPU usage reached 100%.
10 users ended without errors as well. Average response time is 13.357 s. OpenSearch CPU usage reached 100% immediately after test start.
1-100 users Ramp-up.
first error appeared on 16 users;
on 35 users mod-search becomes unstable. * see more details below.
OpenSearch v 1.2 working much slower than Elasticsearch 7.10. See details in last tests.
Environment
mod-search 1.6.4
OpenSearch service
nodes type r6g.large.search (X4) * (4 data nodes 3 dedicated master nodes);
version OpenSearch 1.2 (latest);
kafka 2.8.0
Test Results
Test 1 user
users | Average | 75% | Errors |
1 | 5.509 | 6.164 | None |
Resources usage
Note: This test is not visible on most charts, except CPU usage from OpenSearch service.
Note: OpenSearch CPU usage reached ±70% during test.
*Rest of a charts does not contain any valuable information.
Test 5 users
users | Average | 75% | Errors |
5 | 7.918 | 9.085 | None |
Resources usage
Test 10 users
users | Average | 75% | Errors |
10 | 13.357 | 15.568 | none |
Resources usage
Test 1-100 users (Ramp-Up)
Notable observations:
First errors starts at 16 users;
On 35 users system becomes unstable and containers often failed (See CPU chart);
After 35 users - error rate reached 91%.
ERRORS:
On client side - HTTP 500 Internal Server Error. If the issue persists, please report it to EBSCO Connect.
On server side: ERROR andlerExecutionChain HandlerInterceptor.afterCompletion threw exception
java.lang.NullPointerException: null.
Resources usage
Test 5 users + CICO
users | Average | 75% | Errors |
10 | 11.347 | 13.347 | none |
Test Results openSearch cluster Elasticsearch 7.10
Test 1 user
users | Average | 75% | Errors | Average fse-ptf cluster |
1 | 1.701 | 3.350 | none | 5.509 |
Resources usage
Test 5 users
users | Average | 75% | Errors | Average fse-ptf cluster |
1 | 1.465 | 1.656 | none | 7.918 |
Resources usage