Optimization #4651
open
malloc / memory handling improvement
Added by Peter Manev about 3 years ago.
Updated 3 months ago.
Description
Using tcmalloc/jmalloc for example is improving packet drop a lot on busy systems which suggest potential malloc/memory handling points for improvement.
Peter to create a reproducible setup with trex.
- Tracker changed from Bug to Optimization
- Affected Versions deleted (
5.0.7, 6.0.3, git master)
Do you have more details on your ideas?
So you see a big difference on setups that don't use either tcmallor or jemalloc?
Just for info - this issue is actually less about using tcmalloc/jemalloc and more about finding out if something can be optimized on suricata's side.
- Assignee set to OISF Dev
- Target version set to TBD
Also available in: Atom
PDF