F perf test

Summary

Some performance tests.

Test Environment

Analog zum monitor run the test as follows with the testbed configured. set -a && . ./secrets.sh && python performance-tests/test.py

It is automatically checked that the memory usage is not larger than 1GB and there will be output related to the run times.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

assigned to @henrik

added 1 commit

• 5d6a84c0 - FIX: add ini for docker

Compare with previous version

added 1 commit

• 42a4f27e - FIX: add ini for docker

Compare with previous version

requested review from @salexan

added 15 commits

• 42a4f27e...82c62a95 - 14 commits from branch dev
• 94c56e49 - Merge branch 'dev' into f-perf-test

Compare with previous version

added 1 commit

• 655d9468 - MAINT: remove unused file

Compare with previous version

https://gitlab.indiscale.com/caosdb/customers/f-fit/management/-/issues/34

marked the checklist item All automated tests pass as completed

marked the checklist item Reference related issues as completed

changed the description

marked the checklist item I understand the intent of this MR as completed

marked the checklist item All automated tests pass as completed

marked the checklist item The test environment setup works and the intended behavior is reproducible in the test as completed

@henrik How am I supposed to read the output? When running the tests, the terminal is flushed with debugging output so that's not possible to read the actual performance test output (except for the last line). Of course I could implement something using grep or so myself, but can't we add a convenient way to interpret the output of the tests?

added 1 commit

• e9262853 - TST: write output to file

Compare with previous version

resolved all threads

mentioned in commit d0e5c660

merged