Open Source Document Management System | OpenKM

Hi

I am doing some performance tests on v5.1.9 to see how well it coups with large repository and lots of files. So far I have 15GB repository with approx. 200k files in total.

my repo layout as follows:

okm:root
+ folder_x (1 child)
++ folder_y ( 80 child folders)
+++ folder_a ( approx 2.5k documents in each folder)
...
+++ folder bz


The jackrabbit repository settings LocalFileSystem with FielDataStore on NFS mount
with workspace and versioning and OKM set to use oracle backend.

So far it is very stable , which I am very please with.

I noticed the couple of things, hoping someone would point me to right direction.

When I login to web ui and click on folder_x it returns instantaneously, but when i click on the folder_y it takes about 3-4 minutes to returns. There are no documents inside folder_y, just 80 folders. Folder_aa (with approx. 2500 files) takes about 3-4 minutes.

However, when browse repository from Administration tab, it doesn't take that long.

Any ideas to why UI browsing folder take long and how can I improve this.

Thanks,
Jahirul

Obviously the problem is on browser - we demand something for what is not prepared - and in your repository structure. Is not good idea having 2500 nodes in same folder. You must rendering 2500 elements and that's not good scenario for any UI. The only suggestion is you structure better in several folders the 2500 nodes. Imagine you've got all 2500 documents in same OS folder do you think is good scenario for looking for information or it'll be better separate it in several folders ?

Thanks Josep,
I understand where 2500 nodes could be a problem for browser to handle (we will better organise next time) . However, on the other scenario where I click on folder_y which has only 80 child folders, it should return quickly. I am wondering, if it does some sort of pre-caching of folders below?


Thanks again for suggestions.

Much appreciated.
Jahirul

with 80 child folders should run quickly ( I suggest use any browser than IE family has a very bad javascript engine and that could be the cause of your performance problems, you need a lot of memory to running IE ).