Skip to content
This repository has been archived by the owner on Jul 3, 2020. It is now read-only.

Stress tests

David Crome edited this page Mar 20, 2015 · 2 revisions

Summary

The OSIAM stress tests are meant to run for at least 2 weeks to measure the memory usage over time.

To create some last we use 10 users who run in parallel threads performing all operations in a random order.

The single operations are:

  • create a new random user: about 32%
  • search for random Users: about 26%
  • get a single random User: about 26%
  • update a random User: about 9 %
  • replace a random User: about 6 %
  • delete a random User: about 2 %

The different users running to different times. There are about 20 calls every second to the OSIAM server.

Every 12 h (7 p.m, 7 a.m) the memory usage is collected and saved.

Technology

The OSIAM Stress Tests are written in Java. The memory usage is collected by metrics.

Setup

After completing the Installation, you can to register the stress test extension. Simple run the sql file. This script will also clean database. If you just want to register the extension please run the last section of this file 'Extension data for registration purpose'

How to run the stress tests

The stress test project contains a main class called StressRequester. Simply run this class and the Stress Tests will start.

If you wan't to modify the test parameter like the number of users and the number of calls you can do this in this class.

The test results will be written into a 'metricData.csv' file. The Aggregator Job will start a 7 p.m. the day you started. So don't wonder if no csv will be created until this time.

https://github.com/osiam/server/wiki/detailed_reference_installation

Clone this wiki locally