Run results for: Can JavaScript benefit from the ECS pattern 2? With split components position and health

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 (X11; Linux x86_64; rv:143.0) Gecko/20100101 Firefox/143.0

Browser: Firefox 143

Operating system: Linux

Device Platform: Desktop

Date tested: 9 months ago

OO-style

227/s

ECS-style

21/s

View exact numbers

Test name	Executions per second
✓ OO-style	227 Ops/sec
ECS-style	21 Ops/sec

Script Preparation code:

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

Tests:

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