Optimization #4651: malloc / memory handling improvement - Suricata - Open Information Security Foundation

Actions

Copy link

Optimization #4651

open

malloc / memory handling improvement

Added by Peter Manev about 3 years ago. Updated 5 months ago.

Status:

New

Priority:

Normal

Assignee:

OISF Dev

Target version:

TBD

Effort:

Difficulty:

Label:

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.

Actions

Copy link

Updated by Peter Manev about 3 years ago

Tracker changed from Bug to Optimization
Affected Versions deleted (~~5.0.7, 6.0.3, git master~~)

Actions

Copy link

Updated by Andreas Herz about 3 years ago

Do you have more details on your ideas?
So you see a big difference on setups that don't use either tcmallor or jemalloc?

Actions

Copy link

Updated by Peter Manev over 2 years ago

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.

Actions

Copy link