Run results for: OOP-ish SoA vs AoS

Same as usual Float Array base SoA vs AoS but with classes and objects instead of raw number. I was cursious if the benefit of SoA still holds true even with classes. Same as https://www.measurethat.net/Benchmarks/Show/1909/0/soa-vs-aos but with classes. And some window hackery to get around dated benchmarking suite...

Run details:

User agent: Mozilla/5.0 (Linux; arm_64; Android 13; TFY-LX1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.6834.97 YaBrowser/25.2.8.97.00 SA/3 Mobile Safari/537.36

Browser: Yandex Browser 25

Operating system: Android

Device Platform: Mobile

Date tested: one year ago

AoS

1.1M/s

SoA

1.1M/s

View exact numbers

Test name	Executions per second
✓ AoS	1,097,719 Ops/sec
SoA	1,093,798 Ops/sec

Script Preparation code:

'use strict';
window.N = 1000000;

class PointAndVelocity {
    constructor(x, y, vx, vy) {
        this.x = x;
        this.y = y;
        this.vx = vx;
        this.vy = vy;
    }
}

class Point {
    constructor(x, y) {
        this.x = x;
        this.y = y;
    }
}

class Velocity {
    constructor(vx, vy) {
        this.vx = vx;
        this.vy = vy;
    }
}

aos = Array(N).fill(new PointAndVelocity(0, 0, 0, 0))
    .map(() => new PointAndVelocity(Math.random() * 100|0, Math.random() * 100|0, Math.random() * 100|0, Math.random() * 100|0));

// SoA, we try to duplicate the data so numeric differences are out of the question.
points = Array(N).fill(new Point(0, 0)).
    .map((_, i) => new Point(aos[i].x, aos[i].y));
velocities = Array(N).fill(new Velocity(0, 0)).
    .map((_, i) => new Velocity(aos[i].vx, aos[i].vy));

Tests:

SoA
var N = window.N; for (var i = 0; i < N; ++i) { var point = points[i]; var velocity = velocities[i]; point.x += velocity.vx; point.y += velocity.vy; }
AoS
var N = window.N; for (var i = 0; i < N; ++i) { var pav = aos[i] pav.x += pav.vx; pav.y += pav.vy; }