The current baseline
CompareGrids currently presents the supplied September 2026 benchmark snapshot covering 62 grid entries. This editorial update explains what that baseline contains and what can be concluded from it. No new performance run was performed for this article. The available materials do not include a verified preceding snapshot with which to calculate changes, so we are not publishing invented improvements or regressions.
What you can inspect
The summary table brings together scored categories, while Detailed results exposes the underlying operation values. The dataset distinguishes creation, view operations, changes and export-related work at several row counts. It also includes product metadata and status codes for cases that did not produce ordinary timings. Use the methodology alongside the tables to understand the environment and scoring rules.
The supplied setup describes an Intel i9-13900HX processor, 64 GB of RAM, Windows and an Edge/Chrome version 152 environment. Initialization timing excludes page, script and dataset loading. For short actions, the source selects the third-smallest of ten to twenty observations; for longer actions it selects the smallest of roughly three. These are relatively fast observations, not medians or production service-level guarantees.
What this update does not establish
There is no supported before-and-after comparison in the available material. We cannot attribute a timing change to a release, browser update or configuration adjustment without both comparable datasets and a change record. We also cannot infer memory usage from the timing fields. Vendor test harnesses were not included in the supplied archive, which limits independent reproduction from this package alone.
A failure code describes the tested implementation and operation. An unsupported code does not prove that every configuration of the product lacks the capability. A dash is not a zero-millisecond result. These distinctions remain visible in the detailed evidence and should remain visible when results are quoted elsewhere.
What the next measured update needs
A future results update should identify the previous and new snapshots, changed product versions, configuration differences, environment changes and the operations rerun. It should retain raw observations where possible and explain changes in completion status separately from timing changes. Only comparable measurements should be used to calculate percentage improvements.
Until that evidence exists, use this snapshot to shortlist candidates and design your own proof of concept. Follow the changelog for documented site changes and the methodology for interpretation. We aim to check for new grid versions once every three months and retest them where appropriate. There is no fixed publication schedule.