mwrap user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: Sam Saffron <sam.saffron@gmail.com>
Cc: mwrap-public@80x24.org
Subject: Re: Add enable/disable methods
Date: Thu, 10 Oct 2019 08:41:08 +0000	[thread overview]
Message-ID: <20191010084108.ai6glpnm3x4voru7@dcvr> (raw)
In-Reply-To: <CAAtdryPt9ponL=zSLLWmrW5KGRwTEgr1BxYrmujp3mqfCpFkWQ@mail.gmail.com>

Sam Saffron <sam.saffron@gmail.com> wrote:
> Howdy,
> 
> 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
> 
> `MWRAP_OPTIONS=disabled`

Would still have to pay the extra size + tracking overhead
even in no-op mode; since post-enable free() can operate on
pre-enable malloc() results.

> 
> 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
> environments.
> 
> Thoughts?

Should be doable.  Got a bunch of other stuff coming up into the
weekend; but should be able to find some time for it in a week
or two.

  reply	other threads:[~2019-10-10  8:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 22:11 Add enable/disable methods Sam Saffron
2019-10-10  8:41 ` Eric Wong [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://80x24.org/mwrap/

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

  git send-email \
    --in-reply-to=20191010084108.ai6glpnm3x4voru7@dcvr \
    --to=e@80x24.org \
    --cc=mwrap-public@80x24.org \
    --cc=sam.saffron@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mwrap.git/

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).