New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE
Highlighted
Captain
Captain
846 views

People Users - Search response takes long time (5+ seconds)

Hi,

We have recently upgraded from IDM 4.5 to IDM 4.7 on Linux. We have 3 eDirectory servers in the replica and 2 User app servers. We have around 200K users in the Directory.

The people->users search option in idmdash, the search result take bit longer time, more than 5-6 seconds.

As per documents, this search functionality users the inbuilt/default User entity. As per our requirement we have added more attributes into this entity, it has 70+ attributes.

Few of the attributes are: direct reports, direct report's emp type, roles, groups, fn, ln, and others are some custom attributes.

We can not change/remove the attributes on this entity as this is used by other workflows / functionality.

1. Is there a way, we can improve the search performance?

2. Also, is there an option to make People-Users search to use a new entity which has very few basic attributes (fn,ln,fullname,phone,email).?
(I am not sure from designer, somewhere at the back end on the Userapp property/xml or on eDirectory UA config- if this can be changed)

Note: Earlier this search was taking more longer time, after we set the compound index property to false on ism file, the search is little improved and now it takes 5-6 seconds.

Please help. Thanks in advance.

Regards,
DK
Labels (1)
5 Replies
Highlighted
Absent Member.
Absent Member.

dkdng;2496684 wrote:
Hi,

We have recently upgraded from IDM 4.5 to IDM 4.7 on Linux. We have 3 eDirectory servers in the replica and 2 User app servers. We have around 200K users in the Directory.

The people->users search option in idmdash, the search result take bit longer time, more than 5-6 seconds.

As per documents, this search functionality users the inbuilt/default User entity. As per our requirement we have added more attributes into this entity, it has 70+ attributes.

Few of the attributes are: direct reports, direct report's emp type, roles, groups, fn, ln, and others are some custom attributes.

We can not change/remove the attributes on this entity as this is used by other workflows / functionality.

1. Is there a way, we can improve the search performance?

2. Also, is there an option to make People-Users search to use a new entity which has very few basic attributes (fn,ln,fullname,phone,email).?
(I am not sure from designer, somewhere at the back end on the Userapp property/xml or on eDirectory UA config- if this can be changed)

Note: Earlier this search was taking more longer time, after we set the compound index property to false on ism file, the search is little improved and now it takes 5-6 seconds.

Please help. Thanks in advance.

Regards,
DK


I'd start with Indexes.....especially the new Compound Indexes.

https://www.netiq.com/documentation/identity-manager-47/identity_apps_admin/data/netiq-checklist-setup-dashboard-for-identity-applications.html

https://www.netiq.com/documentation/identity-manager-47/identity_apps_admin/data/b2gx737.html

Visit my Website for links to Cool Solution articles.
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

ScorpionSting wrote:

>
> dkdng;2496684 Wrote:
> > Hi,
> >
> > Few of the attributes are: direct reports, direct report's emp type,
> > roles, groups, fn, ln, and others are some custom attributes.
> >
> > We can not change/remove the attributes on this entity as this is used
> > by other workflows / functionality.
> >
> > 1. Is there a way, we can improve the search performance?


1. Add all the indexes (compound and otherwise) as per the documentation.
2. Patch to 4.7.2
3. Do a LDAP trace (on edirectory side)
https://support.microfocus.com/kb/doc.php?id=7007106 and observe the attrs
searched on with wildcard when using the people search and their order.
Construct a new compund index that conatins the first 5 of these attributes (in
the order used in the search). Always must start with Given Name surname.
Offline the old Given Name Surname compound index.

> > 2. Also, is there an option to make People-Users search to use a new
> > entity which has very few basic attributes
> > (fn,ln,fullname,phone,email).?
> > (I am not sure from designer, somewhere at the back end on the Userapp
> > property/xml or on eDirectory UA config- if this can be changed)


This will impact on workflows and other aspects of the IDM Apps setup. It is a
major undertaking and the best approach would be to dupliccate the existing
user entity, update all your workflows and other logic to use that (if they
need these attrs) and then once that is OK, strip down the default user entity
as required.

--
If you find this post helpful, and are viewing this using the web, please show
your appreciation by clicking on the star below
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

On 2019-03-13 06:46, dkdng wrote:
>
> Hi,
>
> We have recently upgraded from IDM 4.5 to IDM 4.7 on Linux. We have 3
> eDirectory servers in the replica and 2 User app servers. We have around
> 200K users in the Directory.
>
> The people->users search option in idmdash, the search result take bit
> longer time, more than 5-6 seconds.
>
> As per documents, this search functionality users the inbuilt/default
> *User *entity. As per our requirement we have added more attributes into
> this entity, it has 70+ attributes.
>
> Few of the attributes are: direct reports, direct report's emp type,
> roles, groups, fn, ln, and others are some custom attributes.
>
> We can not change/remove the attributes on this entity as this is used
> by other workflows / functionality.
>
> 1. Is there a way, we can improve the search performance?
>
> 2. Also, is there an option to make People-Users search to use a new
> entity which has very few basic attributes
> (fn,ln,fullname,phone,email).?
> (I am not sure from designer, somewhere at the back end on the Userapp
> property/xml or on eDirectory UA config- if this can be changed)
>
> Note: Earlier this search was taking more longer time, after we set the
> compound index property to false on ism file, the search is little
> improved and now it takes 5-6 seconds.
>
> Please help. Thanks in advance.
>
> Regards,
> DK
>
>

I've noticed the slowness by just having many user objects in eDir even
outside the "O" that IDM was pointed at.

It seems it does some kind of search that forces eDir to process all
user objects.



--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
Highlighted
Knowledge Partner Knowledge Partner
Knowledge Partner

alekz <alekz@no-mx.forums.microfocus.com> wrote:
> On 2019-03-13 06:46, dkdng wrote:
>>
>> Hi,
>>
>> We have recently upgraded from IDM 4.5 to IDM 4.7 on Linux. We have 3
>> eDirectory servers in the replica and 2 User app servers. We have around
>> 200K users in the Directory.
>>
>> The people->users search option in idmdash, the search result take bit
>> longer time, more than 5-6 seconds.
>>
>> As per documents, this search functionality users the inbuilt/default
>> *User *entity. As per our requirement we have added more attributes into
>> this entity, it has 70+ attributes.
>>
>> Few of the attributes are: direct reports, direct report's emp type,
>> roles, groups, fn, ln, and others are some custom attributes.
>>
>> We can not change/remove the attributes on this entity as this is used
>> by other workflows / functionality.
>>
>> 1. Is there a way, we can improve the search performance?
>>
>> 2. Also, is there an option to make People-Users search to use a new
>> entity which has very few basic attributes
>> (fn,ln,fullname,phone,email).?
>> (I am not sure from designer, somewhere at the back end on the Userapp
>> property/xml or on eDirectory UA config- if this can be changed)
>>
>> Note: Earlier this search was taking more longer time, after we set the
>> compound index property to false on ism file, the search is little
>> improved and now it takes 5-6 seconds.
>>
>> Please help. Thanks in advance.
>>
>> Regards,
>> DK
>>
>>

> I've noticed the slowness by just having many user objects in eDir even
> outside the "O" that IDM was pointed at.
>
> It seems it does some kind of search that forces eDir to process all
> user objects.
>


You have mentioned that before.

Could it be unnecessary dn references that slow it down?

I noticed there was a fix related to this for org chart in 4.7.2

Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Highlighted
Commander
Commander

in 4.7.3 they fixed this, sort of...

https://www.netiq.com/documentation/identity-manager-47/releasenotes_idm473/data/releasenotes_idm473.html

scroll down to the section called  “ Support for Disabling Virtual List View Search “

it stops the vlv searches of users and reverts it back to LDAP, definite improvement (90+ seconds down to almost instant on a 180k user base) . This does not fix the group lookup, however that is in the works from what I understand.

thanks!

/dg

 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.