From: eregontp@... Date: 2020-07-25T09:38:41+00:00 Subject: [ruby-core:99329] [Ruby master Bug#17050] profiler gem Issue #17050 has been updated by Eregon (Benoit Daloze). I'd recommend starting with something specific like `profiler-memory`. `profiler` is very generic but therefore also unclear and will make people think it's a stdlib-like profiler, but I guess it will not be. I also think it's too early to tell if your gem will be "the profiler everyone uses". BTW, stackprof is a CPU sampling profiler, and ruby-prof seems a tracing CPU profiler. As a side note it'd be nice if profiler-like gems work on more than 1 implementation. I think most them only work on CRuby, because they use C APIs that are efficient on CRuby but basically inefficient on other implementations (see https://github.com/oracle/truffleruby/issues/2044#issuecomment-654848324 for details regarding stackprof & TruffleRuby). ---------------------------------------- Bug #17050: profiler gem https://bugs.ruby-lang.org/issues/17050#change-86724 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- I would like to reuse profiler gem namespace: https://rubygems.org/gems/profiler/versions It currently conflicts with `profile/lib/profiler.rb` however this is no longer part of stdlib. cc @ko1 -- https://bugs.ruby-lang.org/ Unsubscribe: