Nuxeo is slow

[Mohamed_Belmokh]

Hello everyone

Please, I need your help.

I am working to update our ECM platform to go from Nuxeo Nuxeo 5.8 to 7.10. For this, I cloned the production instance and I work on.

According to the documentation, I updated my Nuxeo with the latest hotfix (Nuxeo 5.8-HF39), and then I went from Nuxeo 5.8-HF39 to Nuxeo 6.0-HFHF00.

However, I noticed that Nuxeo is slower than before. The average response time has passed from 800 milliseconds to 2 seconds... I installed all HF nuxeo 6 (6.0-HF29) but it's still slow. I updated my hardware configuration by putting twice the RAM and twice the CPU but the result is the same...

I'have installed Nuxeo 7.10 TLS and Nuxeo is more slower...
/> I'have update my postgresql from 9.1 to 9.5 but it's not better...

You can see that I have a big latence in the attached screenshot

[Paco_Alías]

Hi

try creating some indexes in key tables such as hierarchy and all acls related. This will impact directly on performance. Also use elastic as provider and install it in an external node. Find more in https://doc.nuxeo.com/display/NXDOC/Configuring+the+Elasticsearch+Mapping

Regards

[Mohamed_Belmokh]

Hello,

[Florent_Guillau]

You have to find what is slow before it can be improved. Is it the disk, the network, the database, the Java process... If the latter, then you'd have to use a profiling tool like visualvm to find where time is spent.

[Mohamed_Belmokh]

Thanks for your help

[Florent_Guillau]

You have to use a profiling tool like visualvm to find where time is spent. We can't debug a performance problem in the abstract.

[Anahide_Tchertc]

Hi,

For information, on the rendering layer, Nuxeo 6.0 contains an upgrade to JSF 2, which introduces some performance regressions which have been fixed on 8.2. These Optimizations should be available on 7.10 in the coming weeks (disabled by default).

[Marwane_K_A_]

Hi Anahide,

[Mohamed_Belmokh]

Thank you all,

I finally find the source of the problem. It was a hardware problem and not software. I had to move the VM to a new cluster to solve the problem.

bye 🙂