/
Users-search-filter test report

Users-search-filter test report





PERF-130 - Getting issue details... STATUS

Overview

The purpose of this test is to define system behavior under load with user-search-filter workflow. 
During test we find that weak point of this workflow is resource usage, more specifically it's CPU usage on  DataBase side. 

Version

  • mod-users:17.2.1
  • okapi:4.2.2

Test

Test #Virtual UsersDuration (sec)
151800
281800


Results

Test 1

Response times: 

RequestsTotalResponse times (seconds)
Min50th pct75th pct95th pct99th pctMax
authn/login HTTP Request10.2930.2930.2930.2930.2930.293
GET_/Departments9310.0150.0230.0270.0580.6891.441
GET_/groups?limit=40 sortby group9310.0220.0310.0380.0870.5883.063
GET_/tags9310.0150.0220.0250.0360.0869.527
GET_/users?limit=100 offset=100 query=(active="true")9292.9054.7515.0185.4725.8839.457
GET_/users?limit=100 query=(active="true")9312.2994.7494.9615.3475.7866.700
User transaction9297.3359.6259.99610.68211.39321.193


Service CPU usage

 

Most used modules:

  • Mod-Users  - 14-15% (default usage 3%);
  • Mod-OKAPI - 12-13% (default usage 4%).



Service RAM usage

There's no visible memory usage for any of modules.