Follow up on testing environment

[jerryyiransun]

Thanks for the clarification in #54. I understand the goal is to avoid requiring access to a specific cloud provider.

My remaining concern is around how teams can reliably validate timeout compliance before final submission. Since Track A scoring depends on strict runtime limits, differences in CPU microarchitecture, clock speed, cache size, memory bandwidth, and supported instruction sets can significantly affect execution time, even across systems that are all nominally “8-core Linux workstations.”

Without a closer reference point for the evaluation hardware, it’s difficult to know whether a solution that passes locally will still fit within the timeout in the official harness.

[Gaurav-Shah05]

I had the same question. The readme just mentions "The contest organizers will execute each team's binary across the twenty withheld benchmarks on a dedicated 8-core Linux workstation with 32GB of RAM". As the solver's latency tested on a local machine might vary from when tested on the evaluation hardware, it would help to get more details on the hardware and the compilation targets for the compiled binary to be submitted.