Page 1 of 1

Role_User performace issue

Posted: Mon Nov 28, 2016 4:45 am
by sunil
Hi,

Thanks in advance!!!

I'm using OpenKM with over 50 GB of repository size for our internal documentation with MySQL as back-end.

Earlier everything was perfect but now I'm receiving a weird performance issue for Role_User users only.

If i use OpenKM with Role_Admin, everything is working fine but if I use Role_User instead of Role_Admin, Performance decrease very badly.

Let say if i click on a folder, Role_Admin retrieves records lets say in 3 seconds whereas Role_User is taking around 10-15 seconds to get the same data.

I really appreciate If anyone who could help me with this.

Thanks
Sunil

Re: Role_User performace issue

Posted: Tue Nov 29, 2016 4:40 pm
by jllort
Should be something with security evaluation. Did you modified something about security evaluation https://wiki.openkm.com/index.php/Appli ... figuration ?

Re: Role_User performace issue

Posted: Thu Dec 01, 2016 9:16 am
by sunil
No, I haven't changed anything in security.

"Performance with ROLE_ADMIN is good" but worst with ROLE_USER

Even tried to resolve it with fresh OpenKM installation but failed to resolve it.

Re: Role_User performace issue

Posted: Sun Dec 04, 2016 7:06 pm
by jllort
It was happened suddenly ? did you remember any kind of change ?
How many documents do you have ?
It happens with all users with role users ?
Which database are you using ?
Are you using a lot of keywords ? I think this is not the problem but sometimes this is the reason.

I suspect might be some problem with database performance doing queries into security table. In comunity version we do not have embeded tools into OpenKM for metrics ( we have into professional version and heps in this strange cases ).

Re: Role_User performace issue

Posted: Thu Dec 08, 2016 6:15 am
by sunil
Hi,

While doing uploading, I was using administrator account only.

When the data was less(let say less than 0.2 million documents) the performance was good but by the time volume increased, Performance getting worst.

Right now there are around 0.5 million documents.

Haven't notice any change in system configurations. As i mentioned earlier, I have even tried with fresh OpenKM installation but the performance is same.

Yes, its happen with all the user with Role_User.

We are using MySQL.

We thought performance is worst due to too many keywords used in OpenKM so we drop the idea of capturing keywords. Now there are no keywords.

Permission might be the case, but how we can figure it out?

Thanks
Sunil

Re: Role_User performace issue

Posted: Sat Dec 10, 2016 10:06 am
by jllort
500K documents means at least 500K rows in database.

count number of rows of tables:
OKM_NODE_BASE
OKM_NODE_FOLDER
OKM_NODE_DOCUMENT
OKM_NODE_DOCUMENT_VERSION
OKM_NODE_USER_PERMISSION
OKM_NODE_ROLE_PERMISSION

Which is your hardware configuracion ( disk type ( rpm ), cores, ram, cpu type ) ?
What OS do you have installed there ?
Which is the setenv.sh or setenv.bat configuration ?
Are you using this computer only for OpenKM ?
After starting openkm how many free hardware resources do you have ?
How many concurrent users are using the app ?

Re: Role_User performace issue

Posted: Fri Jan 06, 2017 8:27 am
by sunil
Hi,

Happy New Year 2017

Apologies for late reply. Below are the required details.

number of rows of tables:
OKM_NODE_BASE : 6,12,251
OKM_NODE_FOLDER :2,04,714
OKM_NODE_DOCUMENT: 4,07,537
OKM_NODE_DOCUMENT_VERSION : 4,07,537
OKM_NODE_USER_PERMISSION : 10,90,397
OKM_NODE_ROLE_PERMISSION : 10,52,540

What OS do you have installed there ? Windows Server 2012 64bit
Which is the setenv.sh or setenv.bat configuration ?
Are you using this computer only for OpenKM ? Yes
How many concurrent users are using the app ? 5 Users

Re: Role_User performace issue

Posted: Mon Jan 09, 2017 8:27 am
by jllort
Seems database perfomance problem when does a query in security tables. Check the indexes in these tables.
The problem happens when you are retrieving lists ( folder subtree and list documents into ) ?

Re: Role_User performace issue

Posted: Tue Jan 10, 2017 6:10 am
by sunil
Yes, You are right. Whenever system query in permission table, OpenKM taking much time to get the response. Have checked both user and role permission table for indexed. Node column is already indexed in both tables. Let me know if you want to create index on any other columns.

Yeah, If the system have subfolder or document list, The response is too slow and page is taking much time to render the result.

Thanks
Sunil

Re: Role_User performace issue

Posted: Wed Jan 11, 2017 7:46 pm
by jllort
How many subfolders and documents have into ?
Each node goes across security manager to set if you have grants for viewing or not. If you have a huge number then you have there the problem. You should enable pagination from profiles is this scenario ( at least will solve the problem in file browser, with tree is not possible to be solved ).

Re: Role_User performace issue

Posted: Thu Jan 12, 2017 8:01 am
by sunil
I have around 100 subfolders and each subfolder contain 1 more subfolder and inside that we have 4-5 documents.

I have used pagination earlier but it improves performance a little bit in pagination area but not in tree area.

Is there any other way by which i can implement security ?

If apply security as per roles only, will this be able to boost the performance?

Thanks
Sunil

Re: Role_User performace issue

Posted: Fri Jan 13, 2017 7:18 pm
by jllort
With actual community version is difficult discover exactly which is the methods what's taking so much time. Seems might be a database problem, but I'm not totally sure about it. We are at the end of the next OpenKM release what will come with some actual professional feature like hibernate stats and profiling ( what can helps you in your actual situation for discovering the cause of the problem ).

Seems you have a good hardware ( not so much pleased with OS, always better on linux, because it have the best I/O performance, and for DMS the I/O performace is really relevant ). But also consider from the 500.000 documents we considers it begins the party ( sometimes is needed some optimization etc... ).

I can no give to you more clues, I continue thinking might be something with database. My suggestion should be wait until the next release, will not take much time on being done. And after upgrading you will have more tools for detecting the cause of the problem.