Project

General

Profile

Actions

Bug #4731

closed

flows: spare pool not freeing flows aggressively enough

Added by Victor Julien over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 6.0

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 to Suricata - Bug #4732: flows: spare pool not freeing flows aggressively enoughClosedVictor JulienActions
Actions #1

Updated by Victor Julien over 2 years ago

  • Status changed from In Progress to Closed
Actions #2

Updated by Victor Julien over 2 years ago

  • Copied to Bug #4732: flows: spare pool not freeing flows aggressively enough added
Actions

Also available in: Atom PDF