Project

General

Profile

Actions

Feature #14491

closed

MJIT needs internal debugging methods

Added by sam.saffron (Sam Saffron) over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Target version:
-
[ruby-core:85626]

Description

Issue

Doing careful analysis of MJIT performance is very hard cause there is no way of instrumenting this in runtime

Proposal

  1. Add MJIT.enable, MJIT.disable, MJIT.pause methods.

    • MJIT.pause will continue using MJIT for execution but will no longer compile new fragments
  2. Add MJIT.trace or similar that returns a block for key compile start / compile end operations.

MJIT.trace do |klass, method, line, operation, duration|
end

This will allow simpler analysis of MJITs performance.


Related issues 1 (0 open1 closed)

Precedes Ruby master - Feature #14830: RubyVM::MJIT.pause / RubyVM::MJIT.resumeClosedk0kubun (Takashi Kokubun)Actions
Actions

Also available in: Atom PDF