From: takashikkbn@... Date: 2018-06-21T23:44:53+00:00 Subject: [ruby-core:87585] [Ruby trunk Feature#14491][Closed] MJIT needs internal debugging methods Issue #14491 has been updated by k0kubun (Takashi Kokubun). Status changed from Feedback to Closed In r63710, I added your MJIT.pause idea. I think that's useful to identify some performance issues. Let me close this ticket for now and please reopen it if you think of a use case of MJIT.trace. ---------------------------------------- Feature #14491: MJIT needs internal debugging methods https://bugs.ruby-lang.org/issues/14491#change-72590 * Author: sam.saffron (Sam Saffron) * Status: Closed * Priority: Normal * Assignee: k0kubun (Takashi Kokubun) * Target version: ---------------------------------------- ### 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. -- https://bugs.ruby-lang.org/ Unsubscribe: