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

BP module very slow with IcingaDB backend #343

Closed
MarcusCaepio opened this issue Aug 5, 2022 · 1 comment · Fixed by #393
Closed

BP module very slow with IcingaDB backend #343

MarcusCaepio opened this issue Aug 5, 2022 · 1 comment · Fixed by #393
Assignees
Labels
bug Something isn't working
Milestone

Comments

@MarcusCaepio
Copy link

Hi all,
after switching to IcingaDB as the only backend, loading the configured business processes takes very long. On the old backend, they were loaded immediately.

To Reproduce

  1. Have icingadb running as only backend
  2. Check your defined BPs

Expected behavior

Showing the BPs as fast as with the ido backend

  • Icinga Web 2 version and modules (System - About):
    Icinga Web 2 Version 2.11.1
    businessprocess 2.4.0
  • Web browser used:
    Chrome
  • Icinga 2 version used (icinga2 --version):
    version: r2.13.4-1
  • PHP version used (php --version):
    PHP 7.4.3 (cli)
  • Server operating system and version:
    Ubuntu 20.04.4 LTS

Cheers,
Marcus

@MarcusCaepio MarcusCaepio changed the title BP overview very slow with IcingaDB backend BP module very slow with IcingaDB backend Aug 5, 2022
@MarcusCaepio
Copy link
Author

MarcusCaepio commented Aug 5, 2022

Additional info: We figured out, that only one of our BPs takes very long for loading. This BP has many existing parts of other BPs imported. Maybe that's the reason?

@nilmerg nilmerg self-assigned this Aug 8, 2023
@nilmerg nilmerg added the bug Something isn't working label Aug 8, 2023
@nilmerg nilmerg added this to the 2.5.0 milestone Aug 8, 2023
nilmerg added a commit that referenced this issue Aug 8, 2023
There's no need to fetch more data than required.
And issuing count queries only for benchmarks.. -.-

fixes #343
nilmerg added a commit that referenced this issue Aug 9, 2023
There's no need to fetch more data than required.
And issuing count queries only for benchmarks.. -.-
Also bypasses ipl-orm to fetch results now.

fixes #343
nilmerg added a commit that referenced this issue Aug 9, 2023
There's no need to fetch more data than required.
And issuing count queries only for benchmarks.. -.-
Also bypasses ipl-orm to fetch results now.

fixes #343
nilmerg added a commit that referenced this issue Oct 5, 2023
There's no need to fetch more data than required.
And issuing count queries only for benchmarks.. -.-
Also bypasses ipl-orm to fetch results now.

fixes #343

(cherry picked from commit 78ad449)
nilmerg added a commit that referenced this issue Oct 5, 2023
There's no need to fetch more data than required.
And issuing count queries only for benchmarks.. -.-
Also bypasses ipl-orm to fetch results now.

fixes #343

(cherry picked from commit 78ad449)
nilmerg added a commit that referenced this issue Oct 5, 2023
There's no need to fetch more data than required.
And issuing count queries only for benchmarks.. -.-
Also bypasses ipl-orm to fetch results now.

fixes #343

(cherry picked from commit 78ad449)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants