Skip to content

Conversation

@smuppand
Copy link
Contributor

This PR improves the Tiotest performance runner and aligns it with our review expectations (commit order + shared helpers reuse).
What’s included

  • tools/lib_performance.sh
    • Add shared numeric helpers: norm_metric(), is_number(), append_if_number()
    • Keeps logic POSIX/ShellCheck friendly and reusable across performance runners
  • suites/Performance/Tiotest/run.sh
    • Switch to the shared helpers from lib_performance.sh
    • Reduce “unknown” fields in summary when latency is intentionally hidden (no misleading output)
  • Preserve existing run flow, gating, and result generation
    • suites/Performance/Tiotest/tiotest_baseline.conf
    • Align baseline keys/names with runner-emitted metrics (no intent change)
  • CI/LAVA YAML
    • Enable/adjust Tiotest invocation with explicit arguments and correct output artifact handling
  • README.md
    • Document Tiotest usage (local + CI/LAVA), outputs, and baseline gating behavior

Move common numeric/normalization helpers into lib_performance.sh.

- Add norm_metric(), is_number(), append_if_number()
- Keep helpers POSIX/ShellCheck clean and reusable across runners
- No behavior change in existing callers until follow-up commits

Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
…unknown fields

Update Tiotest runner to rely on shared lib_performance helpers.

- Switch to norm_metric()/is_number()/append_if_number() from lib_performance.sh
- Avoid printing misleading 'unknown' when latency fields are intentionally hidden
- Keep baseline gating, iteration flow, and output format unchanged otherwise

Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Update Tiotest baseline configuration to match runner metric naming.

- Ensure {seqwr,seqrd,rndwr,rndrd}_{mbps,iops} keys align with emitted metrics
- Preserve existing threshold intent; no change in performance expectations

Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Wire Tiotest into the CI/LAVA performance workflow.

- Add Tiotest invocation with explicit args and output directory
- Ensure result files are uniquely named/saved for CI artifacts
- Keep execution order consistent with existing performance runners

Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Document Tiotest usage for local runs and CI/LAVA.

- Add example command lines and common options (threads/modes/iterations)
- Describe baseline gating behavior and how to update baseline safely
- Note output artifacts (logs, metrics TSV, summary, .res)

Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant