Sandeep Raman
unread,Oct 23, 2025, 6:22:03 AM (13 days ago) Oct 23Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to stressapptest-discuss
Hi,
I’ve been running stressapptest and observed that BIOS configuration seems to have a major impact on test consistency and throughput.
After adjusting power, memory, and CPU-related BIOS options, my results on Sys1 (288 cores, 1 TB, 16 channels) became both more consistent and higher overall in bandwidth.
I plan to run more controlled tests to isolate which BIOS parameters matter the most.
Before I do that, I’d like to understand better how these BIOS settings might interact with stressapptest behavior.
Could you please clarify:
a. Which system factors most influence the measured memory bandwidth — e.g., CPU frequency scaling, C-states, memory interleaving, or prefetching?
b. Does stressapptest benefit from “Performance” power profiles (i.e., all cores locked at max turbo) or does it already saturate memory regardless of CPU frequency?
c. Could BIOS options like NUMA interleaving, Memory Patrol Scrub, SMT on/off, or LLC prefetchers significantly affect results?
d. How sensitive is the tool to dynamic clock scaling (P-states / CPPC) or memory power-saving modes?
e. Does thread scheduling or memory affinity depend on BIOS topology reporting (e.g., ACPI tables, SRAT/MADT)?
I’d like to ensure my test results are representative of raw hardware capability rather than firmware configuration side effects.
Any guidance on best BIOS settings for stable and consistent stressapptest benchmarking would be greatly appreciated.
Thanks.