Gist c0ec6bb768fd2672307b0807e4ee46fb

100%

Gist c0ec6bb768fd2672307b0807e4ee46fb

✓ Published0🌍 Public

Last edited May 5, 2017

Created on May 5, 2017

This example benchmarks four JavaScript loop styles—a standard `for` loop, a reversed `for` loop, a `for…of` loop, and `forEach`—on a fixed array of ten numbers. It measures execution time by repeating each loop a thousand times via `performance.now()` timestamps, accumulating the total milliseconds. The code defines each loop as a separate function and calls them through a `test` helper, logging the sum to the console. The comparison uses a simple in-memory data array, with no external libraries, focusing on raw loop performance in a JavaScript environment.

AI-generated description

Similar vizzes

Loading thumbnail…

PowerArray vs....

This example benchmarks the `forEach` method across multiple JavaScript libraries—native `Array.prototype.forEach`, `fast.js`, `underscore`, and `lodash`—applied to three data types: plain arrays, `Float32Array`, and a custom `PowerArray` class. It shows that native `forEach` on a plain array is the baseline, while `fast.js` and `underscore` achieve similar or better throughput on arrays, with `powerArray.forEach` leading all variants. The code uses `process.hrtime()` for high-resolution timing and computes operations per second from a 10-million-element dataset. Results highlight that typed arrays (`Float32Array`) generally slow down iteration, except with `lodash` and `underscore`, which still lag behind array-based calls.

HHypercubed

68% match

Loading thumbnail…

PowerArray benchmarks

This visualization benchmarks the performance of different `forEach` implementations across arrays and typed arrays, showing that native methods on standard arrays are slower than optimized libraries like lodash, underscore, and fast.js, while PowerArray’s custom method rivals them. The bar chart compares operations per second (ops/sec) for each tested scenario, sourced from a benchmark suite generated by Node.js’s `Benchmark` module. The code uses `Benchmark.Suite` to run trials on plain arrays, `Uint16Array`, and PowerArray instances, with libraries like `fast.js`, `underscore`, `lodash`, and native `Array.prototype.forEach` called directly or via `.call`. Data comes from the gist’s `Results.txt` output, and the visualization likely plots these numeric results to highlight performance gaps.

HHypercubed

68% match

Loading thumbnail…

Gist e92adbf79e3256a0d3e222f140a0433b

This example visualizes the relative performance of 16 JavaScript event-emitter libraries across two benchmark scenarios, “emit objects” and “emit one parameter,” using the raw output of the benchmark runner. The data, drawn from a gist by Hypercubed, is rendered as a grouped horizontal bar chart where each bar’s length corresponds to operations per second (ops/sec), with libraries sorted by speed and the fastest highlighted. The chart uses a simple SVG-based custom layout (likely with d3-scale for axes and d3-array for sorting) rather than a high-level charting library, directly mapping the numeric values to pixel widths. The visualization does not show error margins or statistical significance, only the raw ops/sec values and the benchmark’s “Fastest is” annotation for each test.

HHypercubed

66% match

Loading thumbnail…

async-for-each

This example demonstrates a sequential asynchronous loop over an array, where each item is processed only after the previous callback completes. It shows how `asyncForEach` awaits a user-provided callback that delays execution using a custom `waitFor` promise wrapper around `setTimeout`. The code uses the native `async`/`await` syntax and a `for` loop to ensure the array `[1, 2, 3]` is logged in order, with a one-second pause between each item. The visible data source is a hardcoded array in the `start` function, and the rendering approach is console output.

AA6Brgeuka

65% match

Loading thumbnail…

Gist 5ef57ecbfb116e6b42706fb6a30b0987

This example demonstrates a common JavaScript scoping pitfall with the `var` keyword, contrasting it with `let`. It shows that declaring multiple variables in a single statement like `var i, r = 0;` only initializes the last variable (`r`), leaving `i` as `undefined`. Consequently, while loops testing `i < 10` never execute, while loops on `r` run ten times, printing "chau". The visualization, presented as a code gist, uses plain JavaScript console output via `console.log` within `while` loops, relying on the browser's or Node.js runtime rather than any external libraries. The gist highlights the importance of explicit initialization for each variable.

MMistyBlunch

64% match

Loading thumbnail…

Gist d6bacd4ce0d5835b801ba028f9b1c81b

This example benchmarks seven JavaScript object-cloning techniques using the `chuhai` benchmarking library, with `lodash`, `Object.assign`, and JSON methods. It compares operations per second for deep and shallow copies of 1,000 parsed CSV records fetched from a remote dataset. The visualization highlights relative performance differences through horizontal bar lengths, with the fastest method labeled explicitly. The code uses `babyparse` for CSV parsing and `platform` to report the runtime environment, while the benchmark logic is orchestrated via `suite.cb` and `s.bench` calls. Results are output as Markdown text, not rendered graphically.

HHypercubed

64% match

Loading thumbnail…

Gist d51a566a307b428d98eaf3aa8d2a59a3

This example benchmarks JavaScript event emitter libraries across multiple test scenarios, including initialization, emitting with context, and emitting single or multiple values to one or more listeners. The code runs benchmark suites using `benchmark.js`, comparing libraries such as `EventEmitter3`, `MiniSignals`, `push-stream`, and `signal-lite`, and reports throughput in operations per second. It highlights the fastest performers per scenario, such as `push-stream` leading in the "emit with context" test. The visualization shows raw performance data from Node.js 6.2.1, rendered as plain-text tables with pass/fail assertions and timing summaries.

HHypercubed

63% match

Loading thumbnail…

JavaScript Arrays

This example demonstrates the JavaScript `Array` data structure by generating a sequence of ten integers and printing each value to the browser console. It uses a custom `range` function to populate the array, then iterates with the `forEach` method to log each element. The code relies on the Console API’s `console.log` for output, requiring the user to open developer tools to view the results. No external libraries are used; the visualization is purely a textual, console-based representation of array iteration.

AAlex-0277911

63% match