Running Benchmark Applications: Benchmark Server

Showing results for 
Search instead for 
Did you mean: 

Running Benchmark Applications: Benchmark Server

Established Member
0 0 1,619


Use the Benchmark Testing with Alfresco page for version compatibility.

  • Java 1.7.0_51 or later
  • MongoDB 2.6.3 or later installed and running on port 27017 on some server: <mongo-host>


Local Deployment

  • Check out source code of Alfresco Benchmark project
  • Build and start a local Tomcat7 instance
git clone
cd alfresco-benchmark
git tag
git checkout V2.0.1
cd server
mvn tomcat7:run<mongo-host>

13:01:06,998 [localhost-startStop-1] [ INFO] [                 MongoClientFactory: 124] - New MongoDB client created using URL: mongodb://localhost/?connectTimeoutMS=5000&socketTi
13:01:07,318 [localhost-startStop-1] [DEBUG] [                LifecycleController: 174] - Started components: appLifeCycleController
Oct 27, 2014 1:01:07 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ['http-bio-9080']

  • Deploy the sample application
git clone
cd alfresco-benchmark
git tag
git checkout V2.0.1
cd sample
mvn tomcat7:run<mongo-host>

Remote Deployment

  • Set up a Tomcat7 server instance with the manager application listening on port 9080 and configure your Maven settings with the manager application credentials.
  • Deploy the application directly into the load driver:
mvn tomcat7:redeploy -DskipTests  -Dbm.tomcat.ip=<bmdriver-host> -Dbm.tomcat.port=9080 -Dbm.tomcat.server=bm-remote

  • Connect to the Alfresco Benchmark Server application

Create and Start a Test Run

  • Connect to the Benchmark Server

  • Create a new test, SAMPLE'' using the sample application alfresco-benchmark-sample-2.0.1-schema: 9
  • In the properties editor page select the 'MongoDB Connection' section and set the to the hostname or ip address of the MongoDB server, <mongo-host>.
  • Create a test run, 01.
  • Click the run button
  • When the test run finishes, click through and download either the CSV or XLSX report.

Handling failures

If the test run fails to progress from SCHEDULED to STARTED, it is normally because the has not been set.  Currently the only way to see the error is to locate the tests log file.

If the test starts but experiences a high number of failures, the failures can be accessed directly in the MongoDB results.  The video, Following up on Failures shows how this can be done.  It is especially useful when the server under load starts to produce errors or fails to respond correctly.  From the MongoDB console, it would look something like this:

 mongo.exe <mongo-data-host>
use bm20-data

Extra Information