Project

General

Profile

Actions
Copy link

Bug #4836

closed

profiling: Invalid performance counter when using sampling

Added by Eric Leblond about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Eric Leblond
Target version:
7.0.0-beta1
Affected Versions:
6.0.4, git master
Effort:
Difficulty:
Label:
Needs backport to 5.0, Needs backport to 6.0

Description

Some signatures are returning a number of ticks that is out of this world when sampling rate is used:
@{
"checks": 1,
"gid": 1,
"matches": 0,
"percent": 49,
"rev": 10,
"signature_id": 2014702,
"ticks_avg": 94793124810508,
"ticks_avg_match": 0,
"ticks_avg_nomatch": 94793124810508,
"ticks_max": 94793124810508,
"ticks_total": 94793124810508
}, {
"checks": 1,
"gid": 1,
"matches": 0,
"percent": 0,
"rev": 10,
"signature_id": 2100327,
"ticks_avg": 6916,
"ticks_avg_match": 0,
"ticks_avg_nomatch": 6916,
"ticks_max": 6916,
"ticks_total": 6916
},@

Related issues 2 (0 open — 2 closed)

Copied to Suricata - Bug #4896: profiling: Invalid performance counter when using samplingClosedShivani BhardwajActions
Copied to Suricata - Bug #4897: profiling: Invalid performance counter when using samplingClosedJeff LucovskyActions
Actions
Copy link

Also available in: Atom PDF