-
Notifications
You must be signed in to change notification settings - Fork 173
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
Improve app performance #1640
Improve app performance #1640
Conversation
Performance changes between 3.9-7.2 and 3.9-7.2-improve-performance branchesNext metrics show the number of requests and the accumulative sum of all the request times. Just for showing the results, we are assuming the requests are not parallel. Actually, most of them are parallel so the times for both branches are lower. Not all the requests are from the Wazuh app, Kibana does some of them. First load including health check
First load with no health check
Go from Overview to Management
Open agents list
Open an agent welcome screen
Open an agent inventory
|
This pull request depends on wazuh/wazuh#3772, do not merge this PR if wazuh/wazuh#3772 is not merged.
Changes
nestedResolve
andip
before being executed, however, it just needswzConfig
andip
. Now the load prior to show the health check is lower than before. In addition, we are now preventing other controllers from being launchingnestedResolve
when the health check was not finished.checkStoredAPI
which heavily relies on the Wazuh API. Now, and thanks to Add new function for giving information about manager and cluster configuration wazuh#3772, we've reduced from 3 API calls to just 1 API call. Also, the logic behind this method is simpler now. This affects the whole app..wazuh
index. Sometimes, we need to make more than one API request, then fetching this information twice was redundant, now it will be faster in all the Wazuh app.config.yml
, I've added a ten seconds cache instead of parsing the file every time it's requested.Impact with the above changes