Moving transit allocates nothing per frame: reusable positions, kept lists, and the frame probe back in testing.js

- Scratch and marker positions are a Cesium-free Vec3 (src/geo/vector.js), so writing a coordinate does not allocate.
- The dirty set and the upsert lists are kept between frames instead of rebuilt; patchDrawnIcons reuses its lookup arrays.
- measureFrames and stopFrameProbe live in src/layers/transit/testing.js again.
- Tests: 3000 moving vehicles stay under 8 KiB per frame of layer allocation; moving 500 icons allocates under 256 B per upsert.
This commit is contained in:
Sameh Khamis committed 2026-11-15 18:27:10 -08:00
1 parent 0ab31d4fb8
commit 725f2f2998
7 files changed
+359 -138

No files matched your search

+15
View File
@@ -9,6 +9,21 @@ export const PI_OVER_TWO = Math.PI / 2;
export const EPSILON14 = 1e-14;
export const vec = (x = 0, y = 0, z = 0) => ({ x, y, z });
/**
* A three-vector of a shape its own, for a position rewritten every frame.
* Every `{x, y, z}` literal in the page shares one hidden shape, and once
* any code stores a non-number in one (libraries the page loads do) each
* number written to any of them is allocated. An instance of this class
* shares its shape with no other code, so writing a new position into it
* allocates nothing. Read as a plain `{x, y, z}` everywhere.
*/
export class Vec3 {
constructor(x = 0, y = 0, z = 0) {
this.x = x;
this.y = y;
this.z = z;
}
}
export const clone = (a) => ({ x: a.x, y: a.y, z: a.z });
export const add = (a, b) => vec(a.x + b.x, a.y + b.y, a.z + b.z);
export const sub = (a, b) => vec(a.x - b.x, a.y - b.y, a.z - b.z);