Project

General

Profile

Optimization #573

Task #570: tracking: memory fragmentation

reduce allocs in signature parsing

Added by Victor Julien about 7 years ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
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

History

#1

Updated by Victor Julien about 6 years ago

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

Updated by Victor Julien almost 6 years ago

  • % Done changed from 0 to 10
#3

Updated by Victor Julien about 4 years ago

  • Target version changed from 3.0RC2 to Soon
#4

Updated by Philippe Antoine 6 months ago

How can we reproduce the logs you quoted ?

#5

Updated by Victor Julien 6 months 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)

Also available in: Atom PDF