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

Engine monitoring inperformant #1548

Closed
simonhir opened this issue Apr 5, 2024 · 1 comment
Closed

Engine monitoring inperformant #1548

simonhir opened this issue Apr 5, 2024 · 1 comment
Assignees
Labels
bug Something isn't working digiwf-engine digiwf-libs

Comments

@simonhir
Copy link
Member

simonhir commented Apr 5, 2024

Describe the bug

The modification and improvement of the engine monitoring within #1229 is currently using very much memory when running. The problem seems to be the large amount of process definitions.

To Reproduce

  • See current avg mem usage of engine
  • Enable i.e. task monitoring with property DIGIWF_PROMETHEUS_PROCESS-ENGINE_PROVIDERS_TASK: 'true'
  • Engine uses about 0.5 Gb more memory

Expected behavior
The additional needed resources when enabling Prometheus monitoring is as low as possible and doesn't restrict the engine performance while delivering all necessary information for a good monitoring.

Acceptance criteria

  • metrics can run without using too much resources or having impact on engine performance
@simonhir simonhir added bug Something isn't working digiwf-engine digiwf-libs labels Apr 5, 2024
@simonhir simonhir mentioned this issue Apr 9, 2024
9 tasks
@simonhir simonhir self-assigned this Apr 10, 2024
@simonhir simonhir mentioned this issue Apr 10, 2024
5 tasks
@simonhir
Copy link
Member Author

@simonhir simonhir mentioned this issue Apr 10, 2024
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working digiwf-engine digiwf-libs
Projects
None yet
Development

No branches or pull requests

1 participant