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

Petrosian in Docker - strange Service UI behaviour and significantly slower response #23023

Open
Fryguy opened this issue May 6, 2024 Discussed in #22992 · 7 comments
Open
Assignees

Comments

@Fryguy
Copy link
Member

Fryguy commented May 6, 2024

Discussed in https://github.com/orgs/ManageIQ/discussions/22992

Originally posted by eggoide April 15, 2024
Hi all, I would like to kindly ask you for a help or advice regarding strange behaviour we are experiencing with Petrosian on Docker.

We have our environment (najdorf-1.3.20220715135859_39a22e6) consisting of 2 servers. As we need to upgrade and move to dockerized solution, I have cloned the current DB and created 2 docker containers with similar CPU/RAM specs as current Najdord environment.

There are certain weird issues in Service UI:

  1. In Service Catalogs, there is a multiple occurence of a service catalog in html code in drawer-pf hide element. The catalogs in this element are not displayed but the element is significantly increasing the html size. There is no such thing in Najdorf.
    Petrosian:
drawer_pf_hide Najdorf: drawer_pf_hide_old
  1. A random form also contains multiple occurence of a text field with ID, that should be unique and that has been unique in Najdorf. In Petrosian, we have them again in drawer-pf hide element. Now, you cannot use automated tools for testing as you cannot select the text field as its ID is no longer unique within the html code.
    Petrosian:
form_element Najdorf: form_element_old

3, Overall speed of the UI that can be seen i.e. in initial Dashboard. It takes more than 34 seconds to load in Petrosian, while the same Dashboard takes 11 seconds in Najdorf. Even though the initial screen is loaded, it continues to load more elements for many minutes (which I guess is a feature and not an issue). However, overall experience is way slower than in the previous version.
Petrosian:
dashboard
Najdorf:
dashboard_old

Anyone has been dealing with similar problems? Any advice would be higly appreciated! Thank you for your time!

@eggoide
Copy link

eggoide commented May 6, 2024

Ok, probably the common cause why Service UI (it is not happening in regular ManageIQ UI) is so slow with multiple html elements is actually that the whole page is being mirrored multiple times in the notification bar. Here are the examples:
Services:
image
image

Service Catalog:
image

Random form:
image

That means that all the services, VMs and form logic is being initiated multiple times which slows down whole UI.
The behaviour is same when accessing ManageIQ via Nginx domain or directly using ManageIQ's hostname. So the webserver does not play any role.

Any idea why is it happening?

@eggoide
Copy link

eggoide commented May 6, 2024

Another related question is - I tried to turn off the notifications temporarily by disabling Service UI notification in the role of the user but it had no effect. Is it possible to turn it off somehow?

@eggoide
Copy link

eggoide commented May 7, 2024

image

@eggoide
Copy link

eggoide commented May 9, 2024

@Fryguy @jeffibm Hi, I have found out that the problem is probably related to the https://github.com/ManageIQ/manageiq-ui-service/pull/1865
As quinteros is not stable and this bug is not fixed in petrosian , is it possible to build it for petrosian?

@eggoide
Copy link

eggoide commented May 10, 2024

I have additional information - we have replace /ui/service in Petrosian with Quinteros version and it seems that it fixed the problem with Notification bar.

@miq-bot miq-bot added the stale label Aug 12, 2024
@miq-bot
Copy link
Member

miq-bot commented Aug 12, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

1 similar comment
@miq-bot
Copy link
Member

miq-bot commented Nov 25, 2024

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants