mlpstorage reports reportgen does not include VectorDB performance metrics in the generated report.
VectorDB runs write performance data such as QPS, latency, and recall to files like statistics.json, enhanced_statistics.json, or vdb_multi_node_summary.json. However, reportgen reconstructs runs from *_metadata.json and only reads metrics from the top-level metrics field there. The VectorDB metadata writer currently records configuration fields but does not copy the benchmark statistics into metadata["metrics"].
As a result, reportgen prints No metrics available, and the generated report lacks VectorDB performance data even though the run output files contain valid metrics.
Related question: are there currently required pass/fail thresholds for VectorDB results? Rules.md mentions that recall should meet a minimum target for the chosen scale/metric, but I could not find the actual target table in the code/config. For latency, p95_latency_ms appears to be a required reported field, but I could not find a rule requiring it to be below a specific threshold.
mlpstorage reports reportgen does not include VectorDB performance metrics in the generated report.
VectorDB runs write performance data such as QPS, latency, and recall to files like statistics.json, enhanced_statistics.json, or vdb_multi_node_summary.json. However, reportgen reconstructs runs from *_metadata.json and only reads metrics from the top-level metrics field there. The VectorDB metadata writer currently records configuration fields but does not copy the benchmark statistics into metadata["metrics"].
As a result, reportgen prints No metrics available, and the generated report lacks VectorDB performance data even though the run output files contain valid metrics.
Related question: are there currently required pass/fail thresholds for VectorDB results? Rules.md mentions that recall should meet a minimum target for the chosen scale/metric, but I could not find the actual target table in the code/config. For latency, p95_latency_ms appears to be a required reported field, but I could not find a rule requiring it to be below a specific threshold.