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

JIT Trace PR v4.26.0 #9485

Merged
merged 1 commit into from
Aug 28, 2023
Merged

JIT Trace PR v4.26.0 #9485

merged 1 commit into from
Aug 28, 2023

Conversation

v-imohammad
Copy link
Contributor

Updating the Linux and Windows JIT trace files for Dev in anticipation of the next v4 release (4.26.0)

Windows

Function Initial Final Difference
DotNet 62 ms 8 ms 54 ms
Node 424 ms 34 ms 390 ms
DotNet-Isolated 420 ms 26 ms 394 ms

Linux

Total lines in latest windows jittracefile = 4802
Total lines in current jittracefile = 7997
Total lines in new jittracefile = 2055
1885 duplicates were skipped
Total lines in updated jittracefile = 8162

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • I have added all required tests (Unit tests, E2E tests)

@v-smanchem v-smanchem requested review from safihamid and balag0 August 25, 2023 17:45
@v-smanchem v-smanchem merged commit b5a280b into dev Aug 28, 2023
@v-smanchem v-smanchem deleted the JITtracePR4.26.0 branch August 28, 2023 16:28
v-smanchem pushed a commit that referenced this pull request Aug 28, 2023
v-smanchem added a commit that referenced this pull request Aug 28, 2023
Co-authored-by: Mohammad Ibrahim <109541540+v-imohammad@users.noreply.github.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.

4 participants