[OPENIDM-14675] Significant performance degradation in creating managed users with external DJ as repo Created: 2020-05-01  Updated: 2020-05-12  Resolved: 2020-05-12

Status: Closed
Project: OpenIDM
Component/s: Module - Repository DS, Performance
Affects Version/s: 7.0.0
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Tinghua Xu Assignee: Chris Drake
Resolution: Duplicate Votes: 0
Labels: CLARK, regression
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

IDM 7.0.0 latest master(revision: 215b7ef)/DS-7.0.0-M2020-6.1, IDM- Java11, CentOS 7

Attachments: File config.cfg.     File config.cfg.7.0.0     File idm-metrics.     File idm-metrics.7.0.0    
Issue Links:
duplicates OPENIDM-13985 Performance degradation in creating m... Closed
Target Version/s:


When compared IDM 7.0.0 performance with IDM, noticed about 13% degradation in throughput and 16% in mean response times when creating managed users with POST(see similar degradation with PUT), we have the following between and 7.0.0

           mean response times(ms)       throughput   56                             532
7.0.0:     65                             462


This should be the cause of performance degradation in other features such as recon(9%) and livesync(19%) from DJ to IDM when external DJ is used as repo.


To test using pyforge:

  1. Use the config file attached
  2. run the command below:
run-pybot.py -v -c perf -s simple_managed_user.CreateManUsersPost OpenIDM 

Comment by Tinghua Xu [ 2020-05-05 ]

As Chris Drake suggested, tested IDM with DS-7.0.0-M2020-6.1, and got mean response time 56 ms and throughput 528 users/second, looks that change DS doesn't help.

Comment by Tinghua Xu [ 2020-05-12 ]

When added the issue, was not aware of the fix for https://bugster.forgerock.org/jira/browse/OPENIDM-13985 was not merged yet.

With the fix for 13985, we now have mean response times/throughput(60ms/493 req/sec) in 7.0.0.  Recon and sync throughput all improved. Don't see Livesync throughput change though, will investigate it further and add another ticket.

Generated at Sun Jun 13 05:19:50 UTC 2021 using Jira 8.16.0#816000-sha1:a455b91378454416b49bbc88d03e653cb9815ed5.