speedscope
ljharb
| speedscope | ljharb | |
|---|---|---|
| 5 | 1 | |
| 5,222 | 16 | |
| - | - | |
| 7.0 | 1.2 | |
| 20 days ago | 2 days ago | |
| TypeScript | ||
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
speedscope
-
Speeding up the JavaScript ecosystem – Polyfills gone rogue
Glad to hear you like it! Those flame graph screenshots are taken from https://www.speedscope.app/ .
- Speedscope (An Interactive Flamegraph Visualizer)
-
Speeding up the JavaScript ecosystem - one library at a time
Looks like speedscope. https://www.speedscope.app/
-
A Trick For Reading Flamegraphs
Flamegraphs simply visualize this process by placing each of these recorded stacks side by side. The resulting visualization looks like "flames", hence a "flame graph". If you do this visualization where the "parent" of all the stack frames is on the top, rather than the bottom, you get a "waterfall graph", because it looks like a waterfall. It's the same thing though. Speedscope and DevTools visualize using the waterfall format, but I still call them flamegraphs anyway.
-
Performance Profiling a Mongoid Issue Using AppProfiler
While doing research on Ruby profiling I found Shopify's blog post on "How to Fix Slow Code in Ruby". Though the entire post was extremely insightful, it lead me to Shopify's app_profiler library, which can be used to automatically profile code and redirect the output to a local instance of speedscope. Having worked previously with Flame Graphs of CPU stack traces collected using perf.
ljharb
-
Speeding up the JavaScript ecosystem – Polyfills gone rogue
I try to focus on the issues rather than individuals, but the root of the problems in the listed eslint plugin libraries points to ljharb.
If you do some simple digging into these libraries, you will find that these types of commits are quite common within them.
https://github.com/jsx-eslint/eslint-plugin-react/commit/e1d...
https://github.com/jsx-eslint/jsx-ast-utils/commit/bad51d062...
https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/commit/...
He would rather see the download count of these polyfill libraries https://github.com/ljharb/ljharb#projects-i-maintain increase, compared to assessing the health of the JavaScript ecosystem.
What are some alternatives?
FlameGraph - Stack trace visualizer
nolyfill - Speed up your package installation process, reduce your disk usage, and extend the lifespan of your precious SSD.
stackprof - a sampling call-stack profiler for ruby 2.2+
Microsoft-Performance-Tools-Linux-Android - Linux, Android and Chromium Performance Tools built using the Microsoft Performance Toolkit. Cross-platform .NET Core + WPA GUI
app_profiler - Collect performance profiles for your Rails application.
eslint-plugin-import - ESLint plugin with rules that help validate proper imports.
eslint-plugin-jsx-a11y - Static AST checker for a11y rules on JSX elements.
Enzyme - JavaScript Testing utilities for React
Ruby Tests Profiling Toolbox - Ruby Tests Profiling Toolbox
rubygems - Library packaging and distribution for Ruby.
jsx-ast-utils - AST utility module for statically analyzing JSX