Benchmark: Maping BooleanArray vs uInt8 Array2 vs uint8 with bitMasking _2

Maping BooleanArray vs uInt8 Array2 vs uint8 with bitMasking _2 (version: 4)

compare the map speed of an array of random true/false values compared to an ArrayBuffer with a uInt8 view of 0 or 1. The results are that the typed array is much much faster. There are two possible reasons I can think of for this. 1) JavaScript boolean type size of 4Bytes where as an element of a uInt8 array is actually 1Byte. 2) The ArrayBuffer is allocating contiguous memory resulting in a better cache hit ratio.

Comparing performance of: `boolean array vs typed Array with uInt8 vs boolean array - Strict vs typed Array with uInt8 - Strict vs weird boolean - Strict vs uint8 .fill() vs weird boolean - .fill`

Created: 8 years ago by: Registered User

Go to the latest result

Script Preparation code:

const size = 1024;

var buffer = new ArrayBuffer(size);
var u8View = new Uint8Array(buffer, 0, size);

var buffer2 = new ArrayBuffer(size);
var u8BoolView = new Uint8Array(buffer2, 0, size/8);

var booleanArray = [];
for (let i=0; i<size; i++) {
  const someVal = Math.random()*1;
  //typed array stores (0 or 1)
  u8View[i] = someVal;
  //boolean array stores (false or true)
  booleanArray.push(someVal == 1);
}

for (let i=0; i<size/8; i++) {
  let some256Val = Math.random()*255;
  for (let j=0; j<8; j++) { 
  }
  let FLAG_A = some256Val &= 128;
  let FLAG_B = some256Val &= 64;
  let FLAG_C = some256Val &= 32;
  let FLAG_D = some256Val &= 16;
  let FLAG_E = some256Val &= 8;
  let FLAG_F = some256Val &= 4;
  let FLAG_G = some256Val &= 2;
  let FLAG_H = some256Val &= 1;
  u8BoolView[i] = (FLAG_A | FLAG_B | FLAG_C | FLAG_D | FLAG_E | FLAG_F | FLAG_G | FLAG_H);
}

Tests:

boolean array
const resultArray = booleanArray.map(s => { return (s == 1); });
typed Array with uInt8
const resultArray = u8View.map(s => { return (s == 1); });
boolean array - Strict
'use strict'; const resultArray = booleanArray.map(s => { return (s == 1); });
typed Array with uInt8 - Strict
'use strict'; const resultArray = u8View.map(s => { return (s == 1); });
weird boolean - Strict
'use strict'; const resultArray = u8BoolView.map(s => { return ((s &= 128) == 1); });
uint8 .fill()
const resultArray = u8View.fill(1);
weird boolean - .fill
const resultArray = u8BoolView.fill(255);

Historical Performance Data aggregated from 6 community runs

Desktop Results:

Chrome 6 runs

weird boolean - .fill

24.9M/s

uint8 .fill()

22.3M/s

weird boolean - Strict

515K/s

boolean array - Strict

405K/s

boolean array

378K/s

typed Array with uInt8

93K/s

typed Array with uInt8 - Strict

80K/s

Fastest: weird boolean - .fill (311.0x faster)

View exact numbers

✓ weird boolean - .fill: 24,851,132 ops/sec
• uint8 .fill(): 22,281,420 ops/sec
• weird boolean - Strict: 515,184 ops/sec
• boolean array - Strict: 404,687 ops/sec
• boolean array : 377,665 ops/sec
• typed Array with uInt8: 93,113 ops/sec
• typed Array with uInt8 - Strict: 79,914 ops/sec

Results show median performance across all community submissions. Run this benchmark yourself to verify on your device.

Rendered benchmark preparation results:

Suite status: <idle, ready to run>

Previous results

Test case name	Result
boolean array
typed Array with uInt8
boolean array - Strict
typed Array with uInt8 - Strict
weird boolean - Strict
uint8 .fill()
weird boolean - .fill

Fastest: N/A

Slowest: N/A

Latest run results:

Run details: (Test run date: one year ago)

User agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36

Browser/OS: Chrome 139 on Linux

View result in a separate tab

weird boolean - .fill

27.4M/s

uint8 .fill()

25.1M/s

weird boolean - Strict

580K/s

boolean array - Strict

431K/s

boolean array

426K/s

typed Array with uInt8 - Strict

90K/s

typed Array with uInt8

78K/s

View exact numbers

Test name	Executions per second
✓ weird boolean - .fill	27,392,968 Ops/sec
uint8 .fill()	25,077,322 Ops/sec
weird boolean - Strict	580,057 Ops/sec
boolean array - Strict	431,249 Ops/sec
boolean array	425,621 Ops/sec
typed Array with uInt8 - Strict	90,247 Ops/sec
typed Array with uInt8	77,757 Ops/sec

Autogenerated LLM Summary (model llama3.1:latest, generated one year ago):

LLMs can make mistakes. Check important info.

Let's break down what is being tested and analyzed.

**Benchmark Definition**

The benchmark compares the performance of different approaches to creating an array of boolean values, specifically:

1. Using a `BooleanArray` (an array of booleans)
2. Using a typed array (`Uint8Array`) with a view on a `Buffer` object
3. Using a typed array (`Uint8Array`) with a specific bitmasking approach

**Test Cases**

The individual test cases compare the performance of these approaches under different conditions:

1. "boolean array" - Creating an array of boolean values using a `BooleanArray`
2. "typed Array with uInt8" - Creating an array of boolean values using a typed array (`Uint8Array`) with a view on a `Buffer` object
3. "boolean array - Strict" and "typed Array with uInt8 - Strict" - The same test cases as above, but running in strict mode (using `'use strict';`)
4. "weird boolean" - Creating an array of boolean values using the bitmasking approach on a typed array (`Uint8Array`) with a specific mask
5. "uint8 .fill()" and "weird boolean - .fill" - Filling arrays of size 1024 with values (1 for `uint8 .fill()` and 255 for `weird boolean - .fill`)

**Library**

No external libraries are used in this benchmark.

**Special JS feature or syntax**

The only special JavaScript feature used is the bitmasking approach, which is demonstrated in the "weird boolean" test case. This involves using bitwise operations (`&`, `|`) to create a mask and apply it to an array of values.

**Analysis**

The results show that using a typed array (`Uint8Array`) with a view on a `Buffer` object (test cases 2, 5) is significantly faster than using a `BooleanArray` (test case 1). The bitmasking approach ("weird boolean" test cases) also shows good performance.

However, running in strict mode (using `'use strict';`) seems to have a negative impact on performance for all test cases except "weird boolean - .fill".

It's worth noting that these results are specific to the browser and device being tested (Firefox 128 on Windows Desktop).

Maping BooleanArray vs uInt8 Array2 vs uint8 with bitMasking _2 (version: 4)

Comparing performance of: boolean array vs typed Array with uInt8 vs boolean array - Strict vs typed Array with uInt8 - Strict vs weird boolean - Strict vs uint8 .fill() vs weird boolean - .fill

Created: 8 years ago by: Registered User

Go to the latest result

boolean array

typed Array with uInt8

boolean array - Strict

typed Array with uInt8 - Strict

weird boolean - Strict

uint8 .fill()

weird boolean - .fill

Historical Performance Data aggregated from 6 community runs

Desktop Results:

Chrome 6 runs

Suite status: <idle, ready to run>

Fastest: N/A

Slowest: N/A

Autogenerated LLM Summary (model llama3.1:latest, generated one year ago):

Related benchmarks

Comparing performance of: `boolean array vs typed Array with uInt8 vs boolean array - Strict vs typed Array with uInt8 - Strict vs weird boolean - Strict vs uint8 .fill() vs weird boolean - .fill`