We have been using version 2.5.0 for a while now, it takes 2 seconds for the login page to load, but for 3.2.1 it takes up to 30 seconds to load, has anyone experience this issue? Or does the tool do some kind of preload? after we login the tool runs normal.
It running on CentOS 8. Any help is much appreciated.
Does your server meet the expected hardware requirements, specifically 16GB RAM and 4 CPUs?
Hi, it has 12GB RAM and 4 CPUs. I’ll increase it to 16BG RAM but I don’t think it will make a difference, I see on the server network monitor a sustained 4Mbps for the 30s while login page is loading, CPU and RAM utilization is low.
I think I’m done with the tool for the moment, I have spend a considerable amount of hours trying to make it work, first with the install and lastly with the loading times, 30 seconds to get the login screen to appear or to change from group to group won’t do, cmdbuild 2.5.1 takes 2 seconds to load, below is an image of the data transfer while the cmdbuild 3.2.1 login screen is loading up. I have the same network settings as our 2.5.1 instance, so it is not a network config issue and the server share the same ESX host.
Hi, have you tried enabling the gzip compression in tomcat? Also we suggest you to try with the latest release of the software, CMDBuild 3.3, released earlier this week on sourceforge.
Thank you so much!!! enabling compression on Tomcat did it, all is working as expected.
Glad it’s working as expected!