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

[Bug]: Critical path is taxing on CPU when expanding span tags #2179

Open
bobrik opened this issue Feb 20, 2024 · 0 comments
Open

[Bug]: Critical path is taxing on CPU when expanding span tags #2179

bobrik opened this issue Feb 20, 2024 · 0 comments
Labels
bug good first issue help wanted

Comments

@bobrik
Copy link
Contributor

bobrik commented Feb 20, 2024

What happened?

We upgraded from v1.46 to v1.54 and some users noticed slowness when expanding tags. With some CPU tracing I was able to pinpoint #1871 as the culprit.

Steps to reproduce

  1. Run Jaeger v1.54
  2. Load a large trace
  3. Try expanding/collapsing spans
  4. Observe slowness

Expected behavior

Everything is snappy as it was.

Relevant log output

No response

Screenshot

image image

Additional context

No response

Jaeger backend version

v1.54

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

No response
@bobrik bobrik added the bug label Feb 20, 2024
@bobrik bobrik mentioned this issue Feb 20, 2024
Merged
@bobrik bobrik changed the title [Bug]: Critical path is taxing on CPU when expanding span tags in large traces [Bug]: Critical path is taxing on CPU when expanding span tags Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug good first issue help wanted
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bobrik @yurishkuro