Expedition - High CPU Usage for mysqld

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Expedition - High CPU Usage for mysqld

L0 Member

Some of the rules that have been rule enriched in the project have thousands of source or destination IP Addresses. When I try to open these rules to modify them the fields don't populate and Expedition freezes up. When I view the CPU usage on the server - mysqld CPU jumps up to greater than 100% after I attempt to open the rule for modification.


The Expedition VM is configured with 16 vCPUs, 4 sockets, 4 cores per socket, and 16GB RAM so I don't think this is a lack of resources. Are there any suggestions on how to handle rules with this many objects?


L6 Presenter

Hi  @bbb1381 , Currently, in Expedition 1, MySQL is 1 threat process, and therefore it is limited to one CPU.
For future releases of Expedition, we are planning to increase the number of used CPUs to take better advantage of the resources.

  • 1 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!