Up In Flame Graphs

We continue our investigation of our build performance. This time, we use node-inspector to profile our build and Brendan Gregg’s flame graphs for visualization. The flame graph confirms our previous results: our time is spent looking up filenames. But it also shows us that synchronous file access may be the culprit. We start on an asynchronous alternative.

  1. LL16JavaScript Workflow 2015

    Fri, 6 Feb ’15
  2. E278Slack === Speed

    Wed, 4 Feb ’15
  3. E279Quick Build

    Mon, 9 Feb ’15
  4. E280Fast Tests

    Wed, 11 Feb ’15
  5. E281Incremental Builds

    Mon, 16 Feb ’15
  6. E282Lint Rules!

    Wed, 18 Feb ’15
  7. E283A Real Programming Language

    Mon, 23 Feb ’15
  8. E284Performance Optimization and Profiling

    Wed, 25 Feb ’15
  9. E285Up In Flame Graphs

    Mon, 2 Mar ’15
  10. E286From Synchronous to Asynchronous

    Wed, 4 Mar ’15
  11. E287From Asynchronous to Synchronous

    Mon, 9 Mar ’15
  12. E288Integrating Our Spike

    Wed, 11 Mar ’15
  13. E289Incremental Tests

    Mon, 16 Mar ’15
  14. E2900.14 seconds

    Wed, 18 Mar ’15