Project

General

Profile

Actions
Copy link

Optimization #1421

closed

performance regression in the git master

Added by Victor Julien about 9 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Victor Julien
Target version:
-
Effort:
Difficulty:
Label:

Description

It looks like the current git master has 2 regressions after the http pipelining work was merged.

The first is related to the removal of the de_state_m lock and would be addressed by https://redmine.openinfosecfoundation.org/issues/1418

The 2nd is visible mostly with DNS traffic with many transactions. Here the new per-tx de_state logic is doing too many list walks. I'm thinking about keeping a "de_state" counter in the state to keep this under control.

Actions
Copy link
 #1

Updated by Victor Julien almost 9 years ago

  • Target version changed from 2.1beta4 to 3.0RC1

This is mostly gone, but I will continue to work on it.

Actions
Copy link
 #2

Updated by Victor Julien over 8 years ago

  • Target version changed from 3.0RC1 to 70
Actions
Copy link
 #3

Updated by Victor Julien almost 8 years ago

  • Status changed from Assigned to Closed
  • Target version deleted (70)

Both issues have been addressed.

Actions
Copy link

Also available in: Atom PDF