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

Stricter span trimming logic in POTel #4103

Open
sentrivana opened this issue Feb 27, 2025 · 0 comments
Open

Stricter span trimming logic in POTel #4103

sentrivana opened this issue Feb 27, 2025 · 0 comments
Labels
Project: POTel

Comments

@sentrivana
Copy link
Contributor

sentrivana commented Feb 27, 2025 •
edited
Loading

  • currently, we trim to MAX_SPANS per parent, meaning the tree can still be quite huge if nodes have a lot of children
  • we might want to change the trimming logic so that we trim more in order to lower the memory footprint of the tree map

It might also be it's ok as is; we should test and decide. Opening this issue as a reminder.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Project: POTel
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sentrivana