-
Notifications
You must be signed in to change notification settings - Fork 11.8k
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.
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
[v10.2.x] Field: Fix perf regression in getUniqueFieldName() #81417
Conversation
Co-authored-by: nmarrs <nathanielmarrs@gmail.com> (cherry picked from commit 0530021)
@@ -1,4 +1,5 @@ | |||
import { DefaultTimeZone, TimeRange, toUtc, SupplementaryQueryType } from '@grafana/data'; | |||
import { TimeRange, toUtc, SupplementaryQueryType } from '@grafana/data'; | |||
import { defaultTimeZone } from '@grafana/schema'; | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's up with all of these import changes? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is a failing test, so i'm trying to cherry-pick a possibly related cleanup to try to fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🫡
Backport 0530021 from #81323
Addresses https://github.com/grafana/support-escalations/issues/9134
this fixes a large perf regression in
getFieldDisplayName()
introduced in #75511@ryantxu should we backport this?
NOTE: easiest to review each commit separately. the first one is the fix, the second one is an additional optimization for huge-field-count frames.