Hi,

As Florent said, you can get better results.

If you are testing query, you want the database to be fast :

• check that you are not using the embedded DB
• check that you applied the configuration advices for your database
• check that your disks are not slowed down by an other process (like an Antivirus)

I don't know much about the tests you are running, so I can not tell you what numbers you should get.

But for sure, if you tell us more, you should be able to get better :)

We don't have a lot of automated performance tests running via the CMIS connector. The default CMIS perf suite is available here : https://github.com/nuxeo/tools-nuxeo-cmis-jmeter

The tests are basic, but don't hesitate to make a pull request to add more tests.

They are run automatically by the CI chain and result can be see here : http://qa.nuxeo.org/jenkins/job/FT-nuxeo-master-funkload-cmis-bench/lastSuccessfulBuild/artifact/report/

These tests are (by default) run on small boxes (Jenkins build agents).

Tiry

We can't really conclude anything from these numbers without knowing much more. These certainly aren't numbers representative of what Nuxeo is capable of.

What performance testing methodology was used? What was run, how many times? How were measurements taken?

Also what was the server configuration, and Nuxeo configuration? System memory? Memory allocated to Java? What database was used and with what configuration? Was the database tuned? Were specific indexes added?

If your servers are running Windows please make sure that no antivirus is present.