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

New JIT trace PR for -4.37.0,4.637.0,4.837.0 #10626

Open
wants to merge 1 commit into
base: in-proc
Choose a base branch
from

Conversation

v-amakhan
Copy link

@v-amakhan v-amakhan commented Nov 13, 2024

JitTrace 4.37.0, 4.637.0, 4.837.0

Windows JitTrace

Function Function JIT times (ms) JIT Counts Placeholders
Before After Difference Before After Difference Before After
functiondev-pgo-v6-cold-zip_TraceData_2024_11_11_20_54_30.etl 59 11 48 124 49 75 mawsFnPlaceholder4_f_v4_x86 mawsFnPlaceholder6_f_v4_x86
functiondev-pgo-v8-cold-zip_TraceData_2024_11_11_21_30_55.etl 69 31 38 195 120 75 mawsFnPlaceholder7_f_v4_dotnet_8.0_x86 mawsFnPlaceholder7_f_v4_dotnet_8.0_x86

Linux JitTrace

  • Total lines in latest windows jittracefile = 1216
  • Total lines in current jittracefile = 10922
  • Total lines in new jittracefile = 4285
  • 0 code analysis lines were skipped
  • 4175 duplicates were skipped
  • Total lines in updated jittracefile = 11032
  • Writing updated jittrace file contents to D:\a_work\1\out\jittrace\worker-files\ef9c6b3250bb495b8b99e20e42c39dc9.jittrace

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

  • Backporting to the in-proc branch is not required
    • Otherwise: Link to backporting PR
  • 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
  • My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

Copy link
Contributor

@eliaslopezgt eliaslopezgt left a comment

Choose a reason for hiding this comment

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

Initial times of JitTraces are weird, we need to investigate.

Copy link
Contributor

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment.

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.

3 participants