GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add value recording to the trace recording JIT front-end · Issue #144179 · python/cpython

Add value recording to the trace recording JIT front-end #144179

New issue
Copy link
New issue
Copy link
Closed
Closed
Add value recording to the trace recording JIT front-end#144179
Copy link
Assignees
markshannon
Labels
3.15bugs and security fixesbugs and security fixesperformancePerformance or resource usagePerformance or resource usagetopic-JIT

Description

@markshannon
markshannon
opened on Jan 23, 2026
Issue body actions

As listed here: #139109 (comment)

Currently we use a bunch of ad-hoc tracking of objects in the tracing front-end to allow subsequent optimizations, we also maintain ancillary data structures for version number to object lookup for functions, code objects and classes.

This is all very fragile, complicated and inefficient.

By recording references to any necessary objects in the trace, we can:

  • Eliminate optimization failures due to missing values in lookup caches
  • Remove version lookup caches
  • Remove ad-hoc handling of code objects around calls in the tracer
  • Allow the tracer to record any references we feel are useful for optimization
  • Remove tracking of dependencies during tracing

Linked PRs

  • GH-144179: Add value recording to JIT tracing front-end #144303
  • GH-144179: Use recorded values to make optimizer more robust #144437
Reacted by stonebig

Activity

  1. markshannon
    added
    performancePerformance or resource usagePerformance or resource usage
    topic-JIT
    3.15bugs and security fixesbugs and security fixes
    on Jan 23, 2026
  2. markshannon
    self-assigned this
    on Jan 23, 2026
  3. markshannon
    added a commit that references this issue on Feb 2, 2026

    GH-144179: Add value recording to JIT tracing front-end (GH-144303)

    141fd8b
  4. Aniketsy
    added a commit that references this issue on Feb 3, 2026

    pythonGH-144179: Add value recording to JIT tracing front-end (python…

    c6f9612
  5. markshannon
    added a commit that references this issue on Feb 5, 2026

    GH-144179: Use recorded values to make optimizer more robust (GH-144437)

    b53fc7c
  6. markshannon
    closed this as completedon Feb 5, 2026
  7. encukou
    added a commit that references this issue on Feb 5, 2026

    pythonGH-144179: Use recorded values to make optimizer more robust (p…

    cc6697f
  8. thunder-coding
    added 2 commits that reference this issue on Feb 15, 2026

    pythonGH-144179: Add value recording to JIT tracing front-end (python…

    b675ed3

    pythonGH-144179: Use recorded values to make optimizer more robust (p…

    d377d8c
  9. ljfp
    added a commit that references this issue on Apr 25, 2026

    pythonGH-144179: Use recorded values to make optimizer more robust (p…

    efb983d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @markshannon
    markshannon

Labels

3.15bugs and security fixesbugs and security fixesperformancePerformance or resource usagePerformance or resource usagetopic-JIT

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.