-
Notifications
You must be signed in to change notification settings - Fork 32
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
Update cluster CSV parser tool and test thresholds #2468
Comments
Issue updateA method was added to the CSVParser class in order to sum up the parent and children processes. Not sure about how to present the CPU total, as seeing it as an addition can be confusing when it exceeds 100%. 10 workers - 50000 agentsIn order to establish the new thresholds, we will use the data from the following issue: Besides, we will use the data extracted from an environment created yesterday with 50000 agents and 10 workers. This information can be obtained here. Tasks
Resources
Below we can find the results for both environments:
25 workers - 50000 agents
Using the highest values extracted from these two issues, we changed the threshold for this environment in the following way: Tasks
Resources
We can see the output of the test below:
|
Hey team! Please add your planning poker estimate with ZenHub @AdriiiPRodri @Selutario @yanazaeva |
Issue updateThe threshold was updated accordingly to these results: |
In #2032, a tool was developed in charge of iterating, loading and processing CSVs with data on the use of resources of the
wazuh-clusterd
process.However, multiple developments (wazuh/wazuh#10767, wazuh/wazuh#10807, wazuh/wazuh#10920, wazuh/wazuh#11364) have been carried out on the Wazuh cluster that provides it with multiprocessing capabilities.
This has been a boost in its performance. However, it involves creating new child processes that also use resources. These child processes are not taken into account by this tool, hence the need to update it.
Also, when the tool is updated to aggregate information from all processes, the resource thresholds that were set in the performance test (#1939) will probably fall far short. Therefore, it will be necessary to update it.
The text was updated successfully, but these errors were encountered: