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

GUI - search instance always give the first VM name and GUI is very slow #7910

Open
dseralathan opened this issue Aug 24, 2023 · 12 comments · Fixed by #7911
Open

GUI - search instance always give the first VM name and GUI is very slow #7910

dseralathan opened this issue Aug 24, 2023 · 12 comments · Fixed by #7911

Comments

@dseralathan
Copy link

ISSUE TYPE
  • Improvement Request
COMPONENT NAME

Categorize the issue - UI

CLOUDSTACK VERSION

CloudStack 4.18.0.0

CONFIGURATION
OS / ENVIRONMENT

KVM with OEL9

SUMMARY

in GUI - when search instance with particular instance name always give the first VM name in the dashboard
GUI is very slow

STEPS TO REPRODUCE

GUI- Compute-Instances - search tab - give instance name

EXPECTED RESULTS

search should give the exact VM(instance) name

ACTUAL RESULTS

searching one VM gives the other VM name ( the first VM in list )

@boring-cyborg
Copy link

boring-cyborg bot commented Aug 24, 2023

Thanks for opening your first issue here! Be sure to follow the issue template!

@dseralathan
Copy link
Author

Added point : When working on one instance the gUI goes to that first VM in list

@rohityadavcloud
Copy link
Member

rohityadavcloud commented Aug 25, 2023

@dseralathan can you share your ACS and MySQL server versions?

The search results matches with VMs matching/containing the substring, CloudStack keyword search isn't exact. Are other VMs in your search result having the keyword in their names (or displayname)? You've also reported slowness in the API response, how many VMs do you have in your env, and did you try this as a root admin or a normal user account?

@rohityadavcloud
Copy link
Member

@dseralathan does it help improve the response time (slowness of UI) if you add the following in the URL:

http://:8080/client/#/vm?details=min
http://:8080/client/#/vm?details=servoff,tmpl,nics

compared to:
http://:8080/client/#/vm

@weizhouapache weizhouapache linked a pull request Aug 25, 2023 that will close this issue
5 tasks
@weizhouapache weizhouapache added this to the 4.18.1.0 milestone Aug 25, 2023
@weizhouapache
Copy link
Member

@dseralathan
this should be improved by #7911
can you test it ? you can run UI locally following https://github.com/apache/cloudstack/tree/main/ui#development

@DaanHoogland
Copy link
Contributor

@dseralathan closing this as fixed by #7911. please reopen or open a new one as you see fit if needed.

@rohityadavcloud
Copy link
Member

Sorry opening this @DaanHoogland need to hear from @dseralathan thanks

@weizhouapache weizhouapache modified the milestones: 4.18.1.0, 4.18.2.0 Aug 28, 2023
@dseralathan
Copy link
Author

Thanks weizhouapache and DaanHoogland

@DaanHoogland
Copy link
Contributor

Thanks weizhouapache and DaanHoogland

@dseralathan , does it help (see @rohityadavcloud 's questions at #7910 (comment) and #7910 (comment)) I.e. can we close this issue?

@weizhouapache weizhouapache modified the milestones: 4.18.2.0, 4.18.1.0 Aug 29, 2023
@rohityadavcloud
Copy link
Member

Thanks @dseralathan I'm assuming this is acceptable for you, if not pl re-open or raise another issue with more details and steps to reproducing the issue.

@dseralathan
Copy link
Author

the VM search give exact VM and is not changing to the first VM in list after we exclude state,IP in field

@rohityadavcloud
Copy link
Member

We're potentially still seeing this, so re-opening this with the note on investigation - sometimes the table/column could have multiple indexes - when the query choose between 2 or more indexes the wrong one, it could take time for the query to complete. I would investigate if in the case of listVirtualMachines and lisVirtualMachinesMetrics API what queries pick what columns or what indexes the optimiser may choose to run the query. The explain query (https://dev.mysql.com/doc/refman/8.0/en/using-explain.html) can help us know which indexes are in the path of search/optimisation - fixing the index could make the query go faster.

cc @andrijapanicsb @borisstoyanov @vishesh92 @harikrishna-patnala @shwstppr @DaanHoogland

@rohityadavcloud rohityadavcloud modified the milestones: 4.18.3, 4.19.1.0 Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Todo
Status: Todo
Development

Successfully merging a pull request may close this issue.

5 participants