|
|
| (25 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| == Software Requirements == | | = OX App Suite Load Tests = |
| * Java SE JDK6 or JDK7
| |
| * Git
| |
| * SBT
| |
|
| |
|
| == Getting Performance Repository ==
| | We're providing load tests for various OX App Suite APIs and maintain simulations that correspond to specific client implementations. To use it, clone the following repository: |
| * Cloning Repository
| |
| <code>$ git clone https://git.open-xchange.com/git/wd/testing/performance</code>
| |
|
| |
|
| * Checkout a branch, e.g. ''develop''
| | <code> |
| <code>$ git checkout develop</code>
| | $ git clone https://gitlab.open-xchange.com/qa/performance.git |
| | </code> |
|
| |
|
| == Install SBT ==
| | Documentation can be found at <code>com.openexchange.test.performance.gatling/project/doc</code>. Please checkout the branch that corresponds to the version of OX App Suite to be tested. |
| Since we use the Gatling-SBT plugin, which allows us to use Gatling as a testing framework, we'll need to install SBT first.
| |
|
| |
|
| === Installing sbt on Mac ===
| | [[Category: AppSuite]] [[Category: Testing]] |
| * [http://macports.org Macports]
| |
| <code>$ port install sbt</code>
| |
| | |
| * [http://mxcl.github.com/homebrew Homebrew]
| |
| <code>$ brew install sbt</code>
| |
| | |
| === Installing sbt on Windows ===
| |
| * Download the [http://dl.bintray.com/sbt/native-packages/sbt/0.13.5/sbt-0.13.5.msi msi installer] and install it.
| |
| | |
| === Installing sbt on Linux ===
| |
| * [http://dl.bintray.com/sbt/rpm/sbt-0.13.5.rpm RPM] package
| |
| * [http://dl.bintray.com/sbt/debian/sbt-0.13.5.deb DEB] package
| |
| | |
| === Installing sbt manually ===
| |
| * [http://www.scala-sbt.org/0.13/tutorial/Manual-Installation.html Manual] instructions
| |
| | |
| == Build and execute the tests with the SBT-Plugin ==
| |
| After SBT has been successfully installed we can switch to the project's directory:
| |
| <code>$ cd ~/performance/com.openexchange.test.performance.gatling</code>
| |
| | |
| | |
| SBT can be used both as a command line script and as a build console. Most of the commands can be run standalone by passing the command as an argument to SBT, e.g.
| |
| | |
| <code>$ sbt update</code>
| |
| | |
| Note that if a command takes arguments, you need to quote the entire argument path, e.g.
| |
| | |
| <code>$ sbt 'gatling:testOnly com.openexchange.test.performance.gatling.tests.QAPerfOX6'</code>
| |
| | |
| | |
| The following command line script will execute the Gatling OX6 Performance test:
| |
| <code>$ sbt 'set javaOptions ++=Seq("-Dgatling_host=10.0.0.1", "-Dgatling_protocol=http", "-Dgatling_port=80", "-Dgatling_user=100", "-Dgatling_duration_time=120", "-Dgatling_duration_unit=SECONDS")' clean "gatling:testOnly com.openexchange.test.performance.gatling.tests.QAPerfOX6"</code>
| |
| | |
| == Development Environment ==
| |
| If you want to execute/debug the tests via an IDE like Eclipse or IntelliJ IDEA then you will also need to install the following software:
| |
| | |
| === IntelliJ IDEA ===
| |
| Download and install the [http://www.jetbrains.com/idea/download/ IntelliJ IDEA Community Edition]
| |
| | |
| === Eclipse ===
| |
| * [https://www.eclipse.org Eclipse 4.2] or later
| |
| * [http://scala-ide.org Scala IDE plugin]
| |
| | |
| Since there are a few problems with the Scala IDE for eclipse we recommend to use IntelliJ which works out of the box.
| |
| | |
| === Importing Project into IntelliJ ===
| |
| # Open IntelliJ
| |
| # Click on Import Project...
| |
| # Select the gatling folder within the performance repository
| |
| # Import project from external model → SBT Project → Finish
| |
| | |
| == Configurable Parameters ==
| |
| List of all available System-Properties and JVM-Arguments:
| |
| | |
| ; protocol: Which protocol to use. ''Possible values are: '''"http"''' or '''"https"'''. Default value: '''"http"'''.''
| |
| | |
| ; host: Which host to use. ''Possible values are: '''"localhost"''', '''"10.0.0.1"''' or if you want to stress several groupware servers, to bypass a loadbalancer for example, then you can use comma-separated IPs or hostnames '''"10.0.0.1,10.0.0.2,localhost"'''. Default value: '''"localhost"'''.''
| |
| | |
| ; users: How many concurrent users to simulate. ''Default value: '''"5"'''.''
| |
| | |
| ; durationTime: Duration time of the simulation. ''Default value: '''"30"'''.''
| |
| | |
| ; durationUnit: The Unit of the durationTime. ''Possible values are: '''"SECONDS"''', '''"MINUTES"''', '''"HOURS"''' or '''"DAYS"'''. Default value: '''"SECONDS"'''.''
| |
| | |
| ; successpercent: Successful responses in percentage. ''Default value: '''"100"'''.''
| |
| | |
| ; reqpersec: Mean number of requests per second (lower bound). ''Default value: '''"0"'''.''
| |
| | |
| ; resptime: Mean response time (lower bound). ''Default value: '''"0"'''.''
| |
| | |
| ; csv_users: Name of the CSV-File for feeding the requests. ''Default value: '''"ox_user_credentials.csv"'''.''
| |
| | |
| ; syncmsgmax: How many objects to synchronize. ''Relevant only for '''QAPerfUSM'''. Default value: '''"50"'''.''
| |
| | |
| ; pimObjects: How many PIM Objects, e.g. contacts, should be created. ''Default value: '''"5"'''.''
| |
| | |
| == Test Execution ==
| |
| | |
| === Pre-Requisites for the Open-Xchange Groupware Server ===
| |
| ==== Disabling rate limitation ====
| |
| * Modify the parameter maxRateLenientClients @server.properties:
| |
| $ vim /opt/etc/open-xchange/etc/server.properties
| |
| * Specify a new User-Agent which is excluded from rate limit checks
| |
| "GATLING*"
| |
| | |
| ==== Resources/Data ====
| |
| In the data folder you can find an sample csv file which is used to perform a login. If you want to use your own CSV-File place it into the data directory.
| |
| | |
| * Structure of the csv file:
| |
| <code>
| |
| username,password
| |
| user1,secret
| |
| user2,secret
| |
| user3,secret
| |
| ...
| |
| user998,secret
| |
| user999,secret
| |
| user1000,secret
| |
| </code>
| |
| | |
| == Practical hints and tips ==
| |
| * If you want to run tests for more than 24h, uncomment the "timeOut" → "simulation" property at gatling.conf and define a value of more than 24h (in seconds).
| |
| * If you experience OutOfMemory issues when generating charts, adjust "charting" → "accuracy" to a higher value. This will lower the accuracy of the generated graphs. Especially for long-running tests, this could be set to 100ms.
| |