mwrap user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Sam Saffron <>
Subject: Add enable/disable methods
Date: Wed, 9 Oct 2019 09:11:17 +1100	[thread overview]
Message-ID: <> (raw)


In our use case we would like to profile one of N unicorn workers
after a certain timeframe.

Would you be open to adding

`Mwrap.enable` : start profiling memory allocations
`Mwrap.disable` : disable all profiling of memory allocations, making
them as close as possible to a no-op.

and an env var for starting disabled


An additional convenience method here for the entire workflow would be:

`mwrap so_path` that returns the path to the module that needs
preloading, this makes it slightly easier to configure production


             reply	other threads:[~2019-10-08 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 22:11 Sam Saffron [this message]
2019-10-10  8:41 ` Eric Wong
2019-10-10  8:49   ` Sam Saffron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \
    --subject='Re: Add enable/disable methods' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).