-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Cannot Reproduce
-
Affects Version/s: 7.0.0
-
Fix Version/s: 7.0.0
-
Component/s: Module - Relationships, Module - Repository JDBC
-
Labels:
-
Environment:IDM master runs on a CentOS7 machine, Java11, JDBC(MySQL/Postgres) repos, IDM 6.5.0.3
The test preload 30K users with managed roles and managers, then either read the user w/o link expansion as managed/user/A-A-123 or w/ link expansion on roles like managed/user/A-A-123?_fields=,roles/. Between 6.5.0.3 and 7.0.0, we see mean response time(throughput drops) jumped significantly:
| Tests | 6.5.0 Throughput | 6.5.0 Mean response time | 7.0.0 Throughput |
7.0.0 Mean response time | Mean response time(ms) diff in percentage |
| Read w/o expansion | 192 | 155 | 171 | 175 | 13 |
| Read w/ expansion on roles | 195 | 153 | 175 | 170 | 11 |
Attached are the idm metrics collected during the tests and comparisons between 6.5.0 and 7.0(F1 is for 6.5 and F2 is for 7.0).
Read user with link expansion on manager and read user with link expansion on reports showed similar degree response time degradation.
To reproduce the symptom:
Use the config attached and run the following tests between 6.5 and 7.0:
./run-pybot.py -v -c perf -s relationship.ReadManUsersWithRolesManager -t IDM_Read_User_With_No_Link_Expansion OpenIDM
or
./run-pybot.py -v -c perf -s relationship.ReadManUsersWithRolesManager -t IDM_Read_User_With_Roles_Link_Expansion OpenIDM
From the IDM metrics, it looks the degradation might be from different causes, so added this ticket for JDBC repos instead using OPENIDM-14714.
- is related to
-
-
- Closed
-