How to have nice performance on Web UI search

[Former Member]

Hi all,

We run IDM 7.1 SP4 on WAS Java 7.1 running on HPUX 11.3 server with an Oracle 10.4 Database.

We are facing performance issues when we search entrytypes on the WEB UI.

With nice MX_DISPLAYTASK and MX_SEARCHTASK defined, we have poor performance on search (could takes a while).

So, without MX_DISPLAYTASK defined on the object MX_PERSON (detail view of one selected result) it sounds the search results are displayed faster.

Without MX_SEARCHTASK defined, search results sound better but it's not a revolution.

We would like to keep our nice display and search so can we custom attributes of the IDM_datasource?

Do you have any experience with this attributes?

By default, max connexctions is set with "25" and initial connections with "0". Does it make sense for 50 users connected simultaneously ?

Thx for your feedback,

Benjamin

[Former Member]

It sounds that sessions look fine.

My issue is CPU usage on host of the DB when search are performed from the Web UI. 100% used all along the search provides results.

Does any one knows the called procedure or sql request made when search are performed ?

Thanks,

Benjamin

[Former Member]

Hello,

Are you using any query at attribute level to search values?

[Former Member]

Hi,

No we don't. We have only "simple text" attribute or referrals to other entrytypes.

It sounds that if you do not specify any DISPLAY and SEARCH task on entrytype with large catalogue (as MX_PRIVILEGE) time out occurs when users launch search in the web interface,

Benjamin

[Former Member]

Hi,

you should check your database settings.

We had the same issue at a customer but with MSSQL db.

We changed the parallel processing option to =1 and everything was fine.

As described here: http://technet.microsoft.com/en-us/magazine/dd320292.aspx

I am sure something similar also exists for Oracle.

Depending on your hardware setup also temdbs and separate database files can make a positive difference.

By default the installation is not covering DB tuning options. Maybe a database expert can quickly check some common setting and after that you should be fine.

Regards

Ben

[Former Member]

I will have a look in this way,

Thanks for your answer,

Ben