Commit Graph

6 Commits (7a4d81fdd4cf8f8835d70967e03fa0ad4d03f250)

Author SHA1 Message Date
Evilham 29737dc3c5 [stress-tests] Adapt for NC 25
This still supports NC24

While there, configure JMeter to restart threads instead of stopping them.

This keeps the load on the target server.
2023-06-07 15:11:25 +02:00
Elena Barrios Galán eb75377dd3 Revert ":q!Merge branch 'main' into feature/nextcloud_menu_settings"
This reverts commit 4e64f57c55
2023-04-04 07:29:40 +00:00
Evilham d8126abd15
[stress-tests] Adapt for NC 25
This still supports NC24

While there, configure JMeter to restart threads instead of stopping them.

This keeps the load on the target server.
2023-03-31 10:22:13 +02:00
Evilham 5d32e53081
[docs] Fix links in stress-test docs 2023-03-01 23:22:10 +01:00
Evilham 96e5ce8f33
[stress-tests] Fix typo when finding sysbench binary
We were erroneously looking for the sysbench2 binary.

While there unify naming and add direct links from the documentation
to each mentioned file.
2023-03-01 12:39:19 +01:00
Evilham 567bfd770d
[stress-tests] Documentation + necessary files to perform testing
By executing tests in this normalised fashion it is easier to compare
results between different instances or different patch levels.

Roughly speaking there are two kinds of tests:

- VM tests: which summarise general performance of the instance,
  without taking DD into account
- DD tests: which simulates many logins and interactions with DD,
  while recording the session as a user would pereceive it from a
  browser

By using these we should be able to consistently compare and improve
performance.

The original dd-stress-test.tpl.jmx tests file was prepared by
Teradisk  with hardcoded instance, threadcount and duration values.

Testing should now be performed with `vm-test.sh` and `dd-test.sh`
respectively, and the template file should stay generic.
2023-02-28 08:25:42 +01:00