Actions
Bug #4578
closed
JL
JA
perf shows excessive time in IPOnlyMatchPacket
Bug #4578:
perf shows excessive time in IPOnlyMatchPacket
Affected Versions:
Effort:
Difficulty:
Label:
Description
With Suricata 5.0.x, perf shows excessive time spent in IPOnlyMatchPacket when there are rules containing IP addresses as filters. With roughly 400 rules and 15-20K IP addresses, perf showed a majority of time spent in IPOnlyMatchPacket.
Granted, a dataset is a better way to handle large IP address counts used within a rule but 5.0.x support didn't contain official dataset support.
Perhaps a warning or other indicator could be displayed to help users understand the effects of rules with large IP addr counts?
Files
JL Updated by Jeff Lucovsky about 3 years ago
- Status changed from New to In Review
VJ Updated by Victor Julien about 3 years ago
- Assignee set to Justin Azoff
- Target version set to 7.0.0-rc2
VJ Updated by Victor Julien almost 3 years ago
- Status changed from In Review to Closed
- Label Needs backport to 6.0 added
VJ Updated by Victor Julien almost 3 years ago
- Status changed from Closed to Resolved
OT Updated by OISF Ticketbot almost 3 years ago
- Subtask #5997 added
OT Updated by OISF Ticketbot almost 3 years ago
- Label deleted (
Needs backport to 6.0)
JL Updated by Jeff Lucovsky almost 3 years ago
- Label Needs backport to 6.0 added
OT Updated by OISF Ticketbot almost 3 years ago
- Subtask #6005 added
OT Updated by OISF Ticketbot almost 3 years ago
- Label deleted (
Needs backport to 6.0)
VJ Updated by Victor Julien almost 3 years ago
- Status changed from Resolved to Closed
AH Updated by Andreas Herz almost 3 years ago

Added a perf top output to see the impact of the patch
Actions