Bad performance and Slow LDAP response

[jllort]

Second leve cache It's implemeted only in professional edition. By default hibernate comes with first level cache but we consider is not enought for middle great size repositories. Really with professional edition you can parametrize several cache level sizes based on objects, and we have a control of queries, times of query execution etc... I still have not got enought time to complete documentation but will be available at http://wiki.openkm.com/index.php/Utilities_admin then you'll be able to compare this feature among both version.

[jllort]

Hi alexis, can you share your final MySQL configuration parameteres ? I will add as other example in same wiki page, that can help other users.
The information we need is hardware and mysql for your installation. Sizes, for what I understood, 9GB in mysql and 600GB from repository. Which was your number of documents and folders ( that's also interesting ) and the Mysql final parameters. Finally your OpenKM version ( 5.x is quite difference than 6.x which has better performace ).

[shie]

Feedback:

CPU: Intel Xeon E5606 @2.13GHz
RAM: 4GB
System: Windows server 2008, 64bit
JAVA_OPTS=-Xms256m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m -Djava.awt.headless=true -Dfile.encoding=utf-8

my database size:2.5G, my repository size:40GB
100,000 nodes(folders + documents)

At first, I use the default mysql settings and got a bad performance. It taked 45-55 seconds to login openKM. I had traced the hard-disk I/O time, 100% during login time.
Following noxious' guidence, I changes 4 "innodb_" settings, and have a good performance. Now it takes 10 seconds to login openKM.

my.ini settings for mysql:

Code: Select all

query_cache_size=0
table_open_cache=2000
tmp_table_size=16M
thread_cache_size=9
myisam_max_sort_file_size=100G
myisam_sort_buffer_size=32M
key_buffer_size=8M
read_buffer_size=64K
read_rnd_buffer_size=256K
sort_buffer_size=256K
innodb_additional_mem_pool_size=16M
innodb_log_buffer_size=8M
innodb_buffer_pool_size=1042M
innodb_log_file_size=48M
innodb_autoextend_increment=64M

It's may not the best config, but it did improve the performance.
My machine does not have enough physical memory, so I can not set mysql buffer bigger.

BTW, it seems Google Chrome got a better performance browsing taxonomy folder than IE, I think is the browser cache make Chrome fast.

[jllort]

I've extended the wiki documentation at http://wiki.openkm.com/index.php/MySQL_ ... ser_case_2 .Thanks for sharing.