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

Fix profiling json format and enhance perf view #11046

Merged
merged 2 commits into from
Mar 30, 2022
Merged

Conversation

RandySheriffH
Copy link
Contributor

When the inputs of a node are composed of tensors and tensor sequence, profiling numbers in json format will have some invalid comma placed before ']', which result in parsing failure. To tackle the case, let variable "added_type_shapes" do the tracking dedicatedly.
Beyond the fix, reset perf view header whenever user opens a profiling file.

@pranavsharma
Copy link
Contributor

How do we ensure we won't break the format next time?

@RandySheriffH
Copy link
Contributor Author

RandySheriffH commented Mar 30, 2022

How do we ensure we won't break the format next time?

That's a sound concern, pls allow me to come up with a few test cases in a separate PR.

@RandySheriffH RandySheriffH merged commit 9505e8c into master Mar 30, 2022
@RandySheriffH RandySheriffH deleted the FixProfilingIssue branch March 30, 2022 23:15
@@ -60,6 +60,7 @@
preloader.visible(true);

const fileList = event.target.files;
document.getElementById('filename').text = fileList[0].name;
Copy link
Contributor

Choose a reason for hiding this comment

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

Should use spaces instead of tabs.

chilo-ms pushed a commit that referenced this pull request Apr 15, 2022
Co-authored-by: Randy Shuai <rashuai@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants