Skip to content

load_test job from mattermost/6.3.2

Github source: c51ae98 or master branch

Properties

ActionRateMaxVarianceMilliseconds

This is the maximum variance in action rate for each wait period. So if the action rate was 2000ms and the max variance was 500ms. The min and max action rate would be 1500ms and 2500ms.

Default
60000

ActionRateMilliseconds

How often each entity should take an action. For example, for an entity that only posts this would be the time between posts.

Default
240000

AdminEmail

login email address of an admin user in your mattermost system (will be created if not yet present)

Default
success+[email protected]

AdminPassword

password for the admin user above

Default
ltpassword

NumActiveEntities

number of active entities to use (not sure how this is different than NumUsers)

Default
20000

NumChannelsPerTeam

how many channels to create per team

Default
4000,

NumTeams

how many teams to emulate

Default
1,

NumUsers

number of users to emulate

Default
20000

SSHKey

public ssh (id_rsa) key for the ssh user

SSHUsername

username to create on the mattermost server

ServerURL

public url your users normal log in to

Default
http://localhost:8065

SkipBulkload

if you know the users, teams, etc have already been created, you can skip bulk loading them

Default
false

TestLengthMinutes

how long to run the test in minutes

Default
20

WebsocketURL

public url for websockets, generally the same as ServerURL, but with ws replacing the http

Default
ws://localhost:8065

sleep_after_seconds

for debugging purposes, this will sleep before the load test ends

Default
0

sleep_before_seconds

for debugging purposes, this will sleep before the load test starts

Default
0

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/load_test/ directory (learn more).

  • bin/run (from bin/run)
  • config/loadtestconfig.json (from config/config.json.erb)
  • .ssh/id_rsa (from ssh_key.erb)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.