Project

General

Profile

Actions

Bug #4873

open

smb: midstream probing check affects performance

Added by Peter Manev about 3 years ago. Updated over 1 year ago.

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

Description

Have been chasing this for a bit.
I have a reproducible case repay with trex (configs are available in the internal OISF QA lab) where simply removing commit https://github.com/OISF/suricata/commit/5c95c28387a4a756e39fd5f2c984bb8b034aa485 results in what it seems better performance (10-12% less drops)
This may or may not be expected/intended , so it needs more investigation. However just removing the commit and redoing the same test immediately result in better perf stats.
It is especially visible if a box is optimized for max performance with the current HW and then the commit added (suri recompiled and the test re-run).


Related issues 1 (1 open0 closed)

Related to Suricata - Task #5682: tracking: smb performance issuesAssignedVictor JulienActions
Actions #1

Updated by Victor Julien about 2 years ago

  • Related to Task #5682: tracking: smb performance issues added
Actions #2

Updated by Victor Julien almost 2 years ago

  • Subject changed from smb midstream probing check affects performance to smb: midstream probing check affects performance
Actions #3

Updated by Philippe Antoine over 1 year ago

  • Assignee set to OISF Dev
  • Target version set to 8.0.0-beta1
Actions

Also available in: Atom PDF