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.

Thanks for your help

Yes, that's what I'm trying to do.

The further I go, the more I think the problem is either nuxeo either the database.

Shibboleth is reached only once during authentication. Apache 2 is fast enough to process my request (I'm the only user logged).

It remains only Nuxeo and the database.

However, I do not think the problem comes from the database because it is the same as that of production.

The last point: Nuxeo … I note that Nuxeo 5.8 is faster than Nuxeo 6.0 I note that Nuxeo 6.0 is faster than Nuxeo 7.10 I see that 7.10 Nuxeo Nuxeo is faster than 8.1 etc …

Did you install an instance of nuxeo 7.10?

For information :

Here are the statistics of the document database generated by Nuxeo. Number of documents: 48928 Number of versions: 14275 Total Files: 95847 Total file size (KB): 116 685.877 Maximum Tree Depth: 16 the largest file size (KB): 1941 152.3 Record the heaviest 1752 children average speed reading documents (doc / s): 1 098.3

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.