Follow-up from the GFQL external benchmark/docs stack.
Scope: before using the external benchmark pages/report as publication-grade material, run a dedicated benchmark-publication hardening pass over the GFQL external comparisons and report surfaces. Keep detailed audit notes private/local; this issue is only the public work item.
Suggested acceptance criteria:
- Revisit the external comparison docs/report after the current GFQL benchmark/perf stack lands.
- Re-check methodology labels for same-machine vs cross-machine comparisons.
- Re-check result labels for best-engine summaries vs per-engine results.
- Re-check parity language so result-size, exact output, and ranking agreement are not conflated.
- Re-check timed-region language for load/build/query phases.
- Re-check saved artifacts and reproduction instructions against the rendered claims.
- Where practical, rerun current graph-benchmark/Pokec/external-comparator artifacts before refreshing the final report.
Related context: #1668 and the GFQL benchmark stack. No immediate behavior change requested here; this is a deferred publication/readiness pass.
Follow-up from the GFQL external benchmark/docs stack.
Scope: before using the external benchmark pages/report as publication-grade material, run a dedicated benchmark-publication hardening pass over the GFQL external comparisons and report surfaces. Keep detailed audit notes private/local; this issue is only the public work item.
Suggested acceptance criteria:
Related context: #1668 and the GFQL benchmark stack. No immediate behavior change requested here; this is a deferred publication/readiness pass.