Project

General

Profile

Actions

Bug #4732

closed

flows: spare pool not freeing flows aggressively enough

Added by Victor Julien about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

When many flows are returned to the spare pool quickly, it can take far to long to free the excess flows. This is because flows are only freed at a rate of about 100 per second max.


Related issues 1 (0 open1 closed)

Copied from Suricata - Bug #4731: flows: spare pool not freeing flows aggressively enoughClosedVictor JulienActions
Actions

Also available in: Atom PDF