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

[Profiling] Fix UI discrepancies in frame information window #142812

Merged
merged 3 commits into from
Oct 6, 2022

Conversation

jbcrail
Copy link
Contributor

@jbcrail jbcrail commented Oct 6, 2022

Summary

This PR addresses three small missing UI features in the frame information window:

image

  • frame type should be shown when the executable name is unavailable

  • function offset should be shown after the function when available

image

@jbcrail jbcrail added release_note:skip Skip the PR/issue when compiling release notes v8.5.0 v8.6.0 labels Oct 6, 2022
@jbcrail jbcrail requested a review from a team as a code owner October 6, 2022 00:19
sourceLine: number;
}) {
const executable = fileID === '' && addressOrLine === 0 ? 'root' : exeFileName;
const functionSourceLine = functionOffset > 0 ? ` (+${sourceLine - functionOffset})` : '';
Copy link
Contributor

@rockdaboot rockdaboot Oct 6, 2022

Choose a reason for hiding this comment

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

I am not convinced that the relative line number is of any use here. E.g. +66 means 66 lines inside the function - to navigate there you have to manually calculate the absolute line number.
Also: since the aggregation ignores the line number, the value is an arbitrary value.

IMO better: show the function's line number after the source file name, e.g. "xyz.py#123"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree about the relative line number. prodfiler used the relative line number in the information window, yet the function line number in the flamegraph labels. Your last suggestion would make the flamegraph label and the information window agree, which is what I decided to go with.

Copy link
Contributor

@rockdaboot rockdaboot left a comment

Choose a reason for hiding this comment

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

Apart from my comment, LGTM

This matches with the value used in the flamegraph labels.
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
profiling 107 108 +1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
profiling 235.4KB 236.0KB +604.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
profiling 12.5KB 12.5KB +34.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@jbcrail jbcrail merged commit 39811a3 into elastic:main Oct 6, 2022
@jbcrail jbcrail deleted the frame-info-window branch October 6, 2022 19:50
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Oct 6, 2022
…#142812)

* Fix UI discrepancies in frame information window

* Fix comment

* Use source line instead

This matches with the value used in the flamegraph labels.

(cherry picked from commit 39811a3)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.5

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Oct 6, 2022
#142914)

* Fix UI discrepancies in frame information window

* Fix comment

* Use source line instead

This matches with the value used in the flamegraph labels.

(cherry picked from commit 39811a3)

Co-authored-by: Joseph Crail <[email protected]>
WafaaNasr pushed a commit to WafaaNasr/kibana that referenced this pull request Oct 11, 2022
…#142812)

* Fix UI discrepancies in frame information window

* Fix comment

* Use source line instead

This matches with the value used in the flamegraph labels.
WafaaNasr pushed a commit to WafaaNasr/kibana that referenced this pull request Oct 14, 2022
…#142812)

* Fix UI discrepancies in frame information window

* Fix comment

* Use source line instead

This matches with the value used in the flamegraph labels.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:skip Skip the PR/issue when compiling release notes v8.5.0 v8.6.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants