Use the Benchmark Testing with Alfresco page for version compatibility.
~ > svn checkout https://svn.alfresco.com/repos/alfresco-open-mirror/benchmark/tests/workflow/tags/V1.1 workflow
~ > cd workflow
~/workflow > mvn tomcat7:run -Dmongo.config.host=<mongo-host>
...
[INFO] Using existing Tomcat server configuration at c:\work\projects\bm-cmis\target\tomcat
...
10:49:10,944 [localhost-startStop-1] [ INFO] [ MongoClientFactory: 124] - New MongoDB client created using URL: mongodb://mongo-host/?conne...
...
10:49:11,294 [localhost-startStop-1] [DEBUG] [ LifecycleController: 174] - Started components: appLifeCycleController
Nov 03, 2014 10:49:11 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ['http-bio-9087']
mvn tomcat7:redeploy -DskipTests -Dbm.tomcat.ip=<bmdriver-host> -Dbm.tomcat.port=9080 -Dbm.tomcat.server=bm-remote
http://bmdriver-host:9080/manager
The example given here will assume the a setup where several test runs are going to be made against a single server for investigative purposes.
http://bmserver-host:9080/alfresco-benchmark-server
Section | Property | Description |
---|---|---|
MongoDB Connection | mongo.test.host | The hostname of a MongoDB server where the test results and general working data will be stored. This should be an IP address that is visible to all load drivers and _may_ be the same MongoDB instance as the configuration database. This value must always be set for new tests, as there is no working default. A value of 'localhost' is dangerous and should not be used except for local testing. |
Test Controls | Test Duration | Maximum time for the test to run. This acts as an emergency shut off if the test is unable to complete the desired operations e.g. if the server-in-test fails to respond to new session requests and each session only times out after 5s. |
Test Duration Unit | The unit in which the Test Duration is expressed: SECONDS, MINTUES, HOURS or DAYS. | |
Alfresco Server Details | Alfresco port | Use 8080 for a default Alfresco server install. |
Alfresco host | The server host name. It is important to use the same host name as used by the Alfresco Sign Up test so that the user data mirror name matches. As mentioned before, this value can be set once at the test level when performing repeated runs against the same server. The hostname must be visible to the load driver instances where the tests are deployed. | |
Workflow Load | Workflow Count | The number of workflows to start. |
Time Between Workflows | Time between creating new workflows (milliseconds). |
Section | Property | Description |
---|---|---|
Workflow Load | Workflow Count | Set this to 20 for a quick trial run. |
The test should start after a few seconds and progress to completion.
If the test fails to progress from SCHEDULED to STARTED, it could be because:
Startup log messages to start can be retrieved directly from the server via the API (TODO: Add to server UI):
http://bmserver-host:9080/alfresco-benchmark-server/api/v1/status/logs?count=5&skip=0&level=INFO&test=WF_10
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 <mongo-data-host>
use bm20-data
db.WF_10.TRIAL_01.find({success:false}).pretty();
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.