Permalink
Commits on Jan 18, 2017
  1. Release v1.0.0

    evantorrie committed Jan 18, 2017
  2. Drop support for v0.10. Use RequestInterrupt()

    RequestInterrupt can safely be called from another thread.  The
    Interrupt callback cannot start the v8 interpreter, but it can use
    such routines as v8::StackTrace::CurrentStackTrace
    evantorrie committed with evantorrie Jan 17, 2017
Commits on Oct 8, 2015
  1. Release v0.2.0

    evantorrie committed Oct 8, 2015
  2. Add process.monitor.gc.{count,elapsed} getters

    Hang a gc object off process.monitor with readonly absolute values since
    the monitr process is started of:
    
    1. count: # of times GC stop-the-world events have occurred
    2. elapsed: cumulative elapsed time in milliseconds spent in GC
    
    By taking a snapshot of these values at two different times (t1 and t2),
    application code can determine count and duration of GC events between
    t1 and t2.
    evantorrie committed Oct 6, 2015
Commits on Sep 23, 2015
  1. Release v0.1.0

    evantorrie committed Sep 23, 2015
Commits on Sep 18, 2015
  1. Migrated to use Nan-2.x and support nodejs-4.0.0

    evantorrie committed Sep 17, 2015
Commits on May 5, 2015
  1. 0.0.15

    evantorrie committed May 5, 2015
  2. Merge pull request #30 from evantorrie/gc

    [NODEJS-317] Add garbage collection stats to monitr
    evantorrie committed May 5, 2015
Commits on May 4, 2015
  1. Add garbage collection stats to monitr

    We hook into the v8 garbage collection prologue/epilogue events and
    track time spent in between those two calls, along with the number of
    times GC is called in between each reporting interval.
    
    The prologue/epilogue hooks are run in the context of the v8 thread,
    whereas the reporting is in a separate thread (the monitr thread).  For
    this reason we need to protect the garbage collection statistics by a
    mutex to prevent the reporter getting half-filled GC statistics.
    evantorrie committed Mar 26, 2015
Commits on Mar 30, 2015
  1. bump version

    evantorrie committed Mar 30, 2015
  2. Merge pull request #27 from yahoo/pthreadsetname

    Set thread name from inside of said thread
    evantorrie committed Mar 30, 2015
Commits on Mar 25, 2015
  1. set thread name from inside of said thread

    evantorrie committed Mar 25, 2015
Commits on Mar 10, 2015
Commits on Mar 9, 2015
  1. Bump version to v0.0.13

    Now require v0.10 or later
    evantorrie committed Mar 9, 2015
  2. Merge pull request #25 from yahoo/nodejs12-fix

    SetDebugEventListener2 removed from v8 for nodejs-v0.11.15 onwards
    evantorrie committed Mar 9, 2015
  3. We should test 0.11.14 and >= 0.11.15

    evantorrie committed Mar 9, 2015
  4. SetDebugEventListener2 removed from v8 for nodejs-v0.11.15 onwards

    In addition, we
      * No longer need an install script, if we have binding.gyp
      * change Travis to build only 0.10 and 0.12 versions
    evantorrie committed Mar 6, 2015
Commits on Dec 5, 2014
  1. version 0.12 release

    evantorrie committed Dec 5, 2014
  2. Merge pull request #24 from yahoo/performanceFix

    Performance fix - disable stack backtraces by default
    evantorrie committed Dec 5, 2014
  3. version 0.8.1+ of vows requires all streams to be drained

    Previously we were ignoring the response coming back from the
    test/dummy HTTP server.  We need to drain the stream and then
    close the HTTP Server in a teardown function in order to
    avoid vows/istanbul hanging, waiting for the streams to finish.
    evantorrie committed Dec 5, 2014
Commits on Nov 25, 2014
Commits on Nov 21, 2014
  1. Whitespace changes

    evantorrie committed Nov 21, 2014
  2. Disable stack backtraces by default

    Stack backtraces require installing a DebugEventListener into the
    main running v8 isolate.  Doing so also results in a significant
    performance dropoff for any code which has frequent "events of
    interest".  This is because v8 does not allow us to limit the events
    listened to just the DEBUGBREAK events, but instead will also
    give us (Before|After)Compile events, ScriptCollected, NewFunction etc.
    
    This commit changes the default to start with backtraces *not* enabled.
    When they are enabled (via monitor.backtrace = true), the
    DebugEventListener will be installed (resulting in reduced performance
    from that point on).  If monitor.backtrace is reset to false, then the
    DebugEventListener will be reset to NULL, and the performance will
    return to normal.
    
    Also added an explicit isolate to NodeMonitor object
    
    This is required for v0.11.14 and later versions of the v8
    engine, since they now require an explicit Isolate object to be
    passed to most v8 API routines.  In our case, it's the
    v8::Debug::DebugBreak() function.
    evantorrie committed Nov 21, 2014
Commits on Sep 8, 2014
  1. Merge pull request #21 from yahoo/pselectfix

    Fix overly verbose logging
    evantorrie committed Sep 8, 2014
  2. bump version number

    evantorrie committed Sep 8, 2014
  3. Fix overly verbose logging

    evantorrie committed Sep 8, 2014
Commits on Aug 29, 2014
Commits on Aug 22, 2014
  1. Merge pull request #19 from evantorrie/versionfix

    Bumped version to allow new npm package to be built
    rohiniwork committed Aug 22, 2014
  2. Bumped version to allow new npm package to be built

    evantorrie committed Aug 22, 2014
Commits on Aug 20, 2014
  1. Merge pull request #18 from evantorrie/hupbacktrace

    Handle SIGHUP events only in primary monitor thread.  Add selective backtrace
    rohiniwork committed Aug 20, 2014
Commits on Aug 13, 2014