Project

General

Profile

Actions
Copy link

Optimization #573

open

Task #570: tracking: memory fragmentation

reduce allocs in signature parsing

Added by Victor Julien about 12 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
OISF Dev
Target version:
TBD
Effort:
Difficulty:
Label:

Description

Looks like we avg to over a 100 allocs per sig.

[14488] 1/10/2012 -- 16:17:26 - (detect.c:607) <Info> (SigLoadSignatures) -- allocs 80434, frees 491
[14488] 1/10/2012 -- 16:17:26 - (detect.c:681) <Info> (SigLoadSignatures) -- Loading rule file: emerging-all.rules
[14488] 1/10/2012 -- 16:17:28 - (detect.c:712) <Info> (SigLoadSignatures) -- 1 rule files processed. 11592 rules successfully loaded, 0 rules failed
[14488] 1/10/2012 -- 16:17:28 - (detect.c:719) <Info> (SigLoadSignatures) -- allocs 1549841, frees 1104965

Related issues 1 (1 open — 0 closed)

Related to Suricata - Optimization #3544: Have small signature match context without allocationNewCommunity TicketActions
Actions
Copy link
 #1

Updated by Victor Julien almost 11 years ago

  • Target version changed from 2.0rc2 to 3.0RC2
Actions
Copy link
 #2

Updated by Victor Julien almost 11 years ago

  • % Done changed from 0 to 10
Actions
Copy link
 #3

Updated by Victor Julien almost 9 years ago

  • Target version changed from 3.0RC2 to 70
Actions
Copy link
 #4

Updated by Philippe Antoine over 5 years ago

How can we reproduce the logs you quoted ?

Actions
Copy link
 #5

Updated by Victor Julien over 5 years ago

I don't think there is an easy way to do that anymore. Right now I would probably go with callgrind. (valgrind --tool=callgrind)

Actions
Copy link
 #6

Updated by Victor Julien about 4 years ago

  • Target version changed from 70 to TBD
Actions
Copy link
 #7

Updated by Philippe Antoine over 1 year ago

  • Related to Optimization #3544: Have small signature match context without allocation added
Actions
Copy link

Also available in: Atom PDF