Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

how to control gdb trace ? #3201

Closed
Ccheers opened this issue Dec 13, 2023 · 4 comments
Closed

how to control gdb trace ? #3201

Ccheers opened this issue Dec 13, 2023 · 4 comments
Assignees
@houseme
Labels
duplicated question

Comments

@Ccheers
Copy link

Ccheers commented Dec 13, 2023

No description provided.

@Ccheers
Copy link
Author

Ccheers commented Dec 13, 2023

每个sql都会打 trace 打太多了

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

Every sql will print trace. There are too many traces.

@weimx2023
Copy link

Hi there, You can try using controlled sampling ratio.#3171

@weimx2023 weimx2023 mentioned this issue Sep 30, 2024
Open
@gqcn
Copy link
Member

gqcn commented Oct 7, 2024

@Ccheers @weimx2023 Yes, sampling radio might be a good choice for this, we'll consider this carefully and we'll be appreciated for any contributions for this. @houseme

closed as duplicated with #3171

@gqcn gqcn closed this as completed Oct 7, 2024
@houseme houseme mentioned this issue Oct 8, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@houseme houseme

Labels
duplicated question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@houseme @Ccheers @gqcn @Issues-translate-bot @weimx2023