PMI as a tool for measuring jit throughput

Open
#139 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
compilers, performance, tooling

Research direction

Start by reading the PMI and crossgen workflows used for CoreCLR JIT throughput measurements. Define what a robust PMI-based measurement should cover and how its results should complement prejitting; the issue is done when PMI provides a reliable way to explore startup JIT throughput.

Written by the indexing model from the issue text.

Description

Most users see the impact of jit throughput primarily when jitting, especially at application startup.

Current practice for measuring jit throughput in CoreCLR relies on prejitting, using crossgen to jit large numbers of methods. PMI offers an alternative and complementary view of jit throughput.

This issue tracks exploring how to make PMI be a robust tool for exploring jit throughput.

Dominant language
C#
Stars
161
Forks
69
Avg merge
1h 56m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/jitutils

All issues in dotnet/jitutils

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.