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.

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

Merged
merged 3 commits into from
Jan 26, 2024

Conversation

grafana-delivery-bot[bot]
Copy link
Contributor

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.

Co-authored-by: nmarrs <nathanielmarrs@gmail.com>
(cherry picked from commit 0530021)
@grafana-delivery-bot grafana-delivery-bot bot requested review from a team as code owners January 26, 2024 22:48
@grafana-delivery-bot grafana-delivery-bot bot added this to the 10.2.x milestone Jan 26, 2024
@grafana-delivery-bot grafana-delivery-bot bot requested review from codeincarnate and adela-almasan and removed request for a team January 26, 2024 22:48
@grafana-delivery-bot grafana-delivery-bot bot requested review from joshhunt, L-M-K-B, leventebalogh, a team, jackw and leeoniya and removed request for a team and leventebalogh January 26, 2024 22:48
@leeoniya leeoniya enabled auto-merge (squash) January 26, 2024 22:53
@grafana-delivery-bot grafana-delivery-bot bot requested review from a team as code owners January 26, 2024 23:10
@@ -1,4 +1,5 @@
import { DefaultTimeZone, TimeRange, toUtc, SupplementaryQueryType } from '@grafana/data';
import { TimeRange, toUtc, SupplementaryQueryType } from '@grafana/data';
import { defaultTimeZone } from '@grafana/schema';

Copy link
Contributor

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? 🤔

Copy link
Contributor

@leeoniya leeoniya Jan 26, 2024

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.

Copy link
Contributor

@nmarrs nmarrs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🫡

@leeoniya leeoniya merged commit 6288bb1 into v10.2.x Jan 26, 2024
10 checks passed
@leeoniya leeoniya deleted the backport-81323-to-v10.2.x branch January 26, 2024 23:41
summerwollin pushed a commit that referenced this pull request Jan 27, 2024
Revert "Chore: Fix some Explore deprecations (#80076)"

This reverts commit 6ad28d5.
@zserge zserge modified the milestones: 10.2.x, 10.2.4 Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants