Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
All platforms receive identical timing values in MAT. Real hardware differs significantly — a Wiwynn GB200 NVL power-on time differs from a Dell R760-BF4. Using uniform timings means controller behavior is never tested against the latency profile of the actual target hardware, and platform-specific bugs (e.g. timeout thresholds set too low for a slow-booting platform) go undetected in integration tests.
Feature Description
As a developer testing NVIDIA Infra Controller on a specific hardware platform (e.g. Wiwynn GB200, Dell R760-BF4, DGX-GB300), I want MAT to apply timing defaults tuned for that platform's HostHardwareType, so that my integration tests reflect the actual latency characteristics of the hardware I'm deploying to.
Describe your ideal solution
Fill in empirically tuned values for each supported platform in PlatformTimingProfile::for_hardware_type()
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
Is this a new feature, an enhancement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem this feature solves
All platforms receive identical timing values in MAT. Real hardware differs significantly — a Wiwynn GB200 NVL power-on time differs from a Dell R760-BF4. Using uniform timings means controller behavior is never tested against the latency profile of the actual target hardware, and platform-specific bugs (e.g. timeout thresholds set too low for a slow-booting platform) go undetected in integration tests.
Feature Description
As a developer testing NVIDIA Infra Controller on a specific hardware platform (e.g. Wiwynn GB200, Dell R760-BF4, DGX-GB300), I want MAT to apply timing defaults tuned for that platform's HostHardwareType, so that my integration tests reflect the actual latency characteristics of the hardware I'm deploying to.
Describe your ideal solution
Fill in empirically tuned values for each supported platform in PlatformTimingProfile::for_hardware_type()
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct