You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We find the regexp tool take lots cpu if log flush too much. We make a test for 6400 logs in 1 second to test the performance for simulating the case of process issue to report too much logs.
We find the regexp tool take lots cpu if log flush too much. We make a test for 6400 logs in 1 second to test the performance for simulating the case of process issue to report too much logs.
It take 1.95 cpu and 88.8 from regexp execution:
Then I try to filter the audit log by strings.containe funcition to skip the regexp, it is reduced to 0.15 cpu which reduce exceed 10X:
So I think we need add a black list to simple fliter the log to skip regexp to protect the npd perforcemance. I will make a pr soon.
The text was updated successfully, but these errors were encountered: