-
Notifications
You must be signed in to change notification settings - Fork 203
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
Memory usage has almost doubled after introducing custom profiles #789
Labels
enhancement
New feature or request
Priority:Medium
under-investigation
under investigation to develop
Milestone
Comments
I created a minimal pseudo-code as follows. I've considered the following changes:
the above code output is as follows. Since memory reduction can be expected, I'll try to implement with this direction.
|
fukusuket
added a commit
that referenced
this issue
Nov 13, 2022
- add: Profile Enum for profile feature - remove: lazy_static value LOADED_PROFILE_ALIAS, PRELOAD_PROFILE, PRELOAD_PROFILE_REGEX. - chg: DetectInfo.ext_field Nested<Vec<CompactString>> to Vec<(CompactString, Profile)> - chg: clear DetectInfo.detail when convert detail in message.rs::insert
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New feature or request
Priority:Medium
under-investigation
under investigation to develop
With the introduction to custom profiles in 1.5.0, Hayabusa has been using about twice as much memory.
In my tests against a 14GB dataset, with 1.4.3, Hayabusa used less than 6 GB but on the current 1.8.0-dev version, it uses about 11.5GB. We are currently investigating how we can reduce the memory usage.
Note: this only happens when there is enough available memory on the system. When there is low memory, Hayabusa will only use around 300~400MB on average in order not to max out memory.
The text was updated successfully, but these errors were encountered: