From: samuel@... Date: 2020-07-25T04:10:28+00:00 Subject: [ruby-core:99324] [Ruby master Bug#17050] profiler gem Issue #17050 has been updated by ioquatix (Samuel Williams). My initial goal is to expose some general data structures for efficiently capturing large memory profiles on top of `ObjectSpace` and `GC` modules, similar to how memory_profiler gem works. I don't mind making separate gem, but it seems like the `profile` and `profiler` gem would be ideal places for different kinds of profilers. Initially I was thinking of making separate gems and trying to provide a unified interface, e.g. - `memory_profiler` -> `profiler-memory` - `stackprof` -> `profiler-stack` - `ruby-prof` -> `profiler-sample` etc. I think that's too ambitious initially, but yeah, that's a longer term idea, with an initial focus on `profiler-memory` of which I've already got working code and just looking how to structure it best for longer term integration. A sideways step would be to provide `rspec-memory` hooks for using these profilers either for general summary or assertions around blocks of code (of which I already maintain the `rspec-memory` gem which does some parts of this). @ko1 said he wants to use `profile` gem, but I'm not sure if he also intended to use `profiler` gem. So, @ko1, can I use one of them, and you can use the other? ---------------------------------------- Bug #17050: profiler gem https://bugs.ruby-lang.org/issues/17050#change-86719 * 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: