Run results for: Can JavaScript benefit from the ECS pattern?

JS arrays are weird and (probably?) not memory-contiguous, but just for kicks, let's see what difference there is (if any) between performing the same action on 1,000,000 objects in an object-oriented style (with the method attached to the object) vs an ECS-style (with the behavior separated from the raw data)

Go to the benchmark

Run details:

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0

Browser: Firefox 100

Operating system: Windows

Device Platform: Desktop

Date tested: 2 years ago

Test name	Executions per second
OO-style	83.6 Ops/sec
ECS-style	98.6 Ops/sec

Script Preparation code:

class Point {
  constructor(x, y) {
    this.x = x;
    this.y = y;
  }
  tick() {
    this.x += 2;
    this.y += 2;
  }
}

var pointClasses = [];
var pointObjects = [];

for (let i = 0; i < 1000000; i++) {
  pointClasses.push(new Point(0, 0));
  pointObjects.push({ x: 0, y: 0 });
}

Tests:

OO-style
pointClasses.forEach((point) => { point.tick(); });
ECS-style
pointObjects.forEach((point) => { point.x += 2; point.y += 2; });

Run results for: Can JavaScript benefit from the ECS pattern?

OO-style

ECS-style