#5916 ipa user-add CLI last long compare to the related LDAP req
Opened 7 years ago by tbordaz. Modified 7 years ago

Freeipa 4.3.90 - DS 1.3.4

The problem is that the duration of 'ipa user-add' is quite important (e.g. 2.5s) compare to the LDAP reqs related to the user-add (typical 0.4s).
This ticket is to evaluate if the overhead ~2s can be reduced

Test case

install ipa server

ipactl stop
<edit dse.ldif to set access log in msec
dn: cn=config
nsslapd-accesslog-level:131076 >
ipactl start

kinit admin
time ipa user-add --first=t --last=b tb3 (the first one is slow ok)
time ipa user-add --first=t --last=b tb4
----------------
Added user "tb4"
----------------
  User login: tb4
  First name: t
  Last name: b
  Full name: t b
  Display name: t b
  Initials: tb
  Home directory: /home/tb4
  GECOS: t b
  Login shell: /bin/sh
  Kerberos principal: tb4@<realm>
  Email address: tb4@<realm>
  UID: 1463604003
  GID: 1463604003
  Password: False
  Member of groups: ipausers
  Kerberos keys available: False

real    0m2.686s
user    0m0.000s
sys 0m0.883s

ipactl stop
edit DS access logs
   search for 'tb4', select the 'conn=x '
   keep in the file only the records between
[27/May/2016:14:21:11 +0200] conn=x fd=89 slot=89 connection from y.y.y.y to z.z.z.z
...
[27/May/2016:14:21:12 +0200] conn=x op=17 UNBIND

Doing the sum of the etime in that subset of request --> 0.4s

Changes in CLI are being done in #4739 which might obsolete the test.

It's possible that the main part takes initialization of API. This will need to be handled in new CLI as well.

Might be postponed to 4.4.1.

4.4.0 was released, moving open tickets to 4.4.1

moving out tickets not implemented in 4.4.1

4.4.2 is a stabilization milestone. If this bug is important stabilization bug then please put it to NEEDS TRIAGE milestone for retriage.

Metadata Update from @tbordaz:
- Issue assigned to someone
- Issue set to the milestone: FreeIPA 4.5 backlog

7 years ago

Login to comment on this ticket.

Metadata