npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@optimal/fn

v0.3.1

Published

Force V8 to try to optimize a function and check optimization status in nodes 4, 6, 8, and 10.

Downloads

4

Readme

@optimal/fn

Build Status npm version Coverage Status

Force V8 to try to optimize a function and check optimization status in nodes 4, 6, 7, and 8.

Use in benchmarking to optimize before running the benchmark.

Use in analysis to test if your functions can be optimized.

See tests for examples of what optimizes and what doesn't. [JS] [CS]

See:

  1. article

  2. another article

  3. node benchmark helper

  4. node 8+ runtime/runtime.h for new optimization status bit mask

    enum class OptimizationStatus {
      kIsFunction = 1 << 0,      // 1
      kNeverOptimize = 1 << 1,   // 2
      kAlwaysOptimize = 1 << 2,  // 4
      kMaybeDeopted = 1 << 3,    // 8
      kOptimized = 1 << 4,       // 16
      kTurboFanned = 1 << 5,     // 32
      kInterpreted = 1 << 6,     // 64
      kMarkedForOptimization = 1 << 7,            //  128
      kMarkedForConcurrentOptimization = 1 << 8,  //  256
      kOptimizingConcurrently = 1 << 9,           //  512
      kIsExecuting = 1 << 10,                     // 1024
      kTopmostFrameIsTurboFanned = 1 << 11,       // 2048
    };

Install

npm install @optimal/fn --save

Usage

// 1. attempt to optimize a function and get its status
var optimize = require('@optimal/fn')

function fn() { }

var result = optimize(fn)

console.log(result)
// {
//    optimized: true,
//    always   : false,
//    maybe    : false,
//    TurboFan : false
// }

// 2. test a function to see if it's optimized:
var someOtherFn = getSomeOtherFn()
result = optimize.check(someOtherFn)

Result Properties

The result may contain these properties:

  1. optimized - true when optimized, false otherwise
  2. always - When function "is optimized" then always will be false. When function is "always optimized" then always will be true. When function will "never be optimized" then always is true (and optimized is false).
  3. maybe - when function is "maybe deoptimized" then maybe is true, otherwise it is false.
  4. TurboFan - when function is "optimized by TurboFan" then this is true, otherwise it is false.

MIT License