Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance report after data pushed to SORMAS [2] #30

Open
6 tasks
JonasCir opened this issue Feb 24, 2021 · 0 comments
Open
6 tasks

Performance report after data pushed to SORMAS [2] #30

JonasCir opened this issue Feb 24, 2021 · 0 comments
Labels
data-generator feature A new feature to be developed (ticket type) general Not directly concerned with any particular functional section of the application

Comments

@JonasCir
Copy link
Collaborator

JonasCir commented Feb 24, 2021

  • Check if there is a framework that might help to reduce development effort (for example Gatling)
  • Gather duration of pushing data
  • Fetch 100 entries after each 100 entries pushed to SORMAS (make it configurable: default 0 = disabled, 100 = chunk size)
  • A textual report in the log after each run:
    • average duration per entry push
    • duration for the fetch data calls (all timestamps).

Example:

Data created.
Cases:       1000, 423 ms per entry
Contacts:    1000, 501 ms per entry
Event part.: 1000, 354 ms per entry

Data fetch duration (100 entries after a chunk of 100 entries pushed):
Cases:       1234ms, 2345ms, 3456ms, .....
Contacts:    ...
Event part.: ...

Total duration: 1234,5 s
@StefanKock StefanKock added data-generator general Not directly concerned with any particular functional section of the application feature A new feature to be developed (ticket type) labels Feb 24, 2021
@StefanKock StefanKock changed the title Performance report after data pushed to SORMAS Performance report after data pushed to SORMAS [2] Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data-generator feature A new feature to be developed (ticket type) general Not directly concerned with any particular functional section of the application
Projects
None yet
Development

No branches or pull requests

2 participants