Skip to content

performance issue: (*HTTP2Response).detect cost too much memory #700

Closed
@chilli13

Description

@chilli13

Run ecapture -m text cost unexcepted cpu/memory resource. After using the tool perfto analyze,(*HTTP2Response).detect consumed a lot of resources. After removing this function (*HTTP2Response).detect and **(HTTP2Request).detect and recompiling the ecapture to run testcase, the performance was significantly improved.
Small files access https server with high concurrency, construct 50Mbps traffic, average memory 550M, maximum memory 677.66M. After optimization (*HTTP2Response).detect and *(HTTP2Request).detect , memory is reduced to 293.016M

Linux Server:

Device: VM
OS: [ctyunos 2.0.1]
Arch: 4.19.90-2102.2.0.0062.ctl2.x86_64 #1 SMP Thu Mar 10 03:34:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Kernel Version: 4.19

  1. modify makefile compile option to obtain symbol information
  2. perf record $(pidof ecapture)
  3. perf report
    image

Metadata

Metadata

Assignees

Labels

help wantedExtra attention is neededquestionFurther information is requested

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions