iovisor / iovisor/bcc

weird result of funcslower.py and funclatency.py

Open
#3,848 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
10d 4h
Merged PRs (30d)
3

Description

# In the environment of centos7.6
I used the BCC tool to check the delay of do_fsync, but I found a lot of outliers, it felt like the program overflowed.
![ugwZ7W4YAy](https://user-images.githubusercontent.com/2580074/153825246-38e2f9e5-7593-4bea-acf3-c83b9c816363.png)
We are using pg_test_fsync to simulate system stress
Then I saw this weird error
We thought it was a problem with funcslower.py
Just replaced it with funclantency.py
But the problem remains
![middle_img_v2_c1808fdc-62ce-4a3c-b75d-515d5701f41g](https://user-images.githubusercontent.com/2580074/153825629-527db310-f48d-49d9-8f77-aea40e4e6ee4.png)
Does anyone know if this is a bug in the program?
Thanks!

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the reported outliers with funcslower.py and funclatency.py on CentOS 7.6 while running pg_test_fsync, using the two attached screenshots as the observed behavior. No source file or test is named; done means determining whether the measurements reflect a program bug and documenting a reproducible result or diagnosis.

Written by the indexing model from the issue text.

Assessment

Tech stack
centos, postgresql, python
Domain
observability-sre, operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.