Hello,
Following the discussion in the OCUDU GitLab issue #571, I noticed that running the testbed—especially OCUDU in debug mode—can be quite demanding on hardware, sometimes leading to runtime issues that are difficult to troubleshoot.
Personally, I experienced these failures on my low-end laptop, but they completely disappeared after I upgraded to a new computer (my benchmark results are available here: Geekbench CPU Benchmark).
Instead of relying only on the static hardware guidelines currently in README.md (lines 74-75), I propose adding an automated performance check. We could use the Geekbench 6 Linux CLI and use the Dell XPS scores discussed in the GitLab issue as our baseline reference point.
Proposed Solution
We could introduce a simple helper script called test_performance.sh to automate this verification.
The script would:
- Verify if Geekbench 6 is installed. If missing, download it directly from the official link.
- Run the Geekbench CLI.
- Parse the single-core and multi-core scores from the generated results link.
- Compare them with our baseline to give the user a quick heads-up if their hardware might be insufficient.
Maintenance
The only minor drawback is that Geekbench baseline scales can shift slightly over time as the benchmark suite is updated. Because of this, the reference scores defined in the script might need a quick review and update about once a year to stay aligned.
As a side note, the inspiration for this check came from tech and gaming reviews on YouTube, where Geekbench is widely used as a standard way to quickly evaluate and compare different systems.
Thank you for considering this new script.
Hello,
Following the discussion in the OCUDU GitLab issue #571, I noticed that running the testbed—especially OCUDU in debug mode—can be quite demanding on hardware, sometimes leading to runtime issues that are difficult to troubleshoot.
Personally, I experienced these failures on my low-end laptop, but they completely disappeared after I upgraded to a new computer (my benchmark results are available here: Geekbench CPU Benchmark).
Instead of relying only on the static hardware guidelines currently in README.md (lines 74-75), I propose adding an automated performance check. We could use the Geekbench 6 Linux CLI and use the Dell XPS scores discussed in the GitLab issue as our baseline reference point.
Proposed Solution
We could introduce a simple helper script called
test_performance.shto automate this verification.The script would:
Maintenance
The only minor drawback is that Geekbench baseline scales can shift slightly over time as the benchmark suite is updated. Because of this, the reference scores defined in the script might need a quick review and update about once a year to stay aligned.
As a side note, the inspiration for this check came from tech and gaming reviews on YouTube, where Geekbench is widely used as a standard way to quickly evaluate and compare different systems.
Thank you for considering this new script.