Good day,
I have the latest version of OpenKM from the community edition:
OpenKM - Knowledge Management
Version: 6.3.12 (build: a3587ce)
I am in the process of migrating from CentOS 7 to AlmaLinux 9. A server with similar characteristics and the same version of OpenKM has been set up on AlmaLinux 9, and this version is already functional. To address bug fixes and avoid migrating the same issues from the production environment, I exported and imported the production files into the migration environment using the OpenKM application, preserving the UUID and additional metadata of these files, such as modification dates and the user who uploaded them.
However, I am facing the following problem: although I increased the Java memory settings for OpenKM, which I edited in the bin directory with the setenv.sh file, and I upgraded the instance type to a larger one on AWS, I also tested with the maximum connections to the database, which is MariaDB. I increased its cache memory to 4GB, but despite these changes, after migrating approximately 900GB of information, it takes a long time to load when I refresh the browser (F5). It then displays the taxonomy and all its documents, but if two users attempt to log in simultaneously, it takes even longer to the point of becoming unusable, which is not acceptable for production.
In the OpenKM log and catalina.out, I haven’t found anything unusual. Initially, there were warnings regarding cache memory, which I resolved. However, I am sharing the following logs to see if anyone can shed light on the problem.
I have the latest version of OpenKM from the community edition:
OpenKM - Knowledge Management
Version: 6.3.12 (build: a3587ce)
I am in the process of migrating from CentOS 7 to AlmaLinux 9. A server with similar characteristics and the same version of OpenKM has been set up on AlmaLinux 9, and this version is already functional. To address bug fixes and avoid migrating the same issues from the production environment, I exported and imported the production files into the migration environment using the OpenKM application, preserving the UUID and additional metadata of these files, such as modification dates and the user who uploaded them.
However, I am facing the following problem: although I increased the Java memory settings for OpenKM, which I edited in the bin directory with the setenv.sh file, and I upgraded the instance type to a larger one on AWS, I also tested with the maximum connections to the database, which is MariaDB. I increased its cache memory to 4GB, but despite these changes, after migrating approximately 900GB of information, it takes a long time to load when I refresh the browser (F5). It then displays the taxonomy and all its documents, but if two users attempt to log in simultaneously, it takes even longer to the point of becoming unusable, which is not acceptable for production.
In the OpenKM log and catalina.out, I haven’t found anything unusual. Initially, there were warnings regarding cache memory, which I resolved. However, I am sharing the following logs to see if anyone can shed light on the problem.
Attachments
(14.2 KiB) Downloaded 58 times
