Vav Labs

Benchmark Lab

Measured numbers first, broader claims later.

The first public result is intentionally narrow: a Godot 4.6.2 diagnostics micro-benchmark for empty-path failure checks. Larger benchmark scenes stay labeled as targets until reproducible captures exist.

Godot 10,000-agent benchmark scene with a frame-time overlay.

Interactive benchmark scene

10,000 agents, one draggable goal, live frame-time readout.

The web export is the visual companion to the native benchmark: flip between naive per-agent path queries and the scheduled shared-field mode, then inspect the published JSON for the measured numbers.

Current measured capture - Godot 4.6.2, 64x64 grid, Windows, AMD Ryzen 5 2600X
Case Grid Iterations Average
Reject GOAL_SOLID before search Validate start/goal and return a named failure reason before AStarGrid2D search. 64x64 10,000 7.31 usec
Raw allow_partial_path solid-goal query Call AStarGrid2D.get_id_path(start, solid_goal, allow_partial_path=true). 64x64 1,000 381.34 usec
Diagnose disconnected region Validate the request, run AStarGrid2D once, and classify the empty path. 64x64 1,000 161.02 usec
NavigationServer sync guard Check NavigationServer2D.map_get_iteration_id(map) before path queries. 64x64 10,000 3.94 usec
Download measured dataset (JSON)
Candidate benchmark scenes - targets only, not public performance claims
Scenario Grid Agents Frequency Target
Tactical map 64x64 100 30 queries/sec <1ms pathfinding budget
RTS skirmish 256x256 500 100 queries/sec <4ms pathfinding budget
Flow-field stress 512x512 1,000 continuous flow <3ms flow-field update
Large-world hierarchical 1024x1024 50 long-range 10 queries/sec <8ms long-path budget

measurement-gap: these larger scenarios are engineering targets. Public result columns, profiler captures, and downloadable benchmark scenes stay unpublished until a reproducible run exists.

Small diff

Each run changes one variable: query budget, graph update strategy, clearance cache, or flow-field reuse.

Reproducible scene

The scene, Godot version, PathForge version, hardware class, and run settings must be visible next to the result.

No soft adjectives

Fast, scalable, and production-ready only mean something when the page carries a measured capture.