I am using the hwinfo SDK to periodically fetch hardware status information from various motherboards. My program is designed to call hwinfo.status() every second to get the current status. This works well with most motherboards, where the hwinfo.status() call typically takes less than 50ms.
However, I have encountered an issue with the GIGABYTE B650E AORUS ELITE X AX ICE motherboard. On this particular motherboard, the hwinfo.status() call takes approximately 2700ms, which significantly affects the performance of my program.
Here is the relevant code snippet:
```javascript
setInterval(async () => {
const startTime = Date.now();
await hwinfo.status();
const tookTime = Date.now() - startTime;
Logger.debug(`get hwinfo.status took ${tookTime} ms`);
}, 1000);
```
Expected Behavior:
The hwinfo.status() call should take less than 50ms, similar to other motherboards.
Actual Behavior:
The hwinfo.status() call takes around 2700ms on the GIGABYTE B650E AORUS ELITE X AX ICE motherboard.
Environment:
Motherboard: GIGABYTE B650E AORUS ELITE X AX ICE
hwinfo SDK Version: [8.12]
Additional Information:
I have tested this on multiple systems with the same motherboard and observed consistent results.
Other motherboards do not exhibit this behavior.
However, I have encountered an issue with the GIGABYTE B650E AORUS ELITE X AX ICE motherboard. On this particular motherboard, the hwinfo.status() call takes approximately 2700ms, which significantly affects the performance of my program.
Here is the relevant code snippet:
```javascript
setInterval(async () => {
const startTime = Date.now();
await hwinfo.status();
const tookTime = Date.now() - startTime;
Logger.debug(`get hwinfo.status took ${tookTime} ms`);
}, 1000);
```
Expected Behavior:
The hwinfo.status() call should take less than 50ms, similar to other motherboards.
Actual Behavior:
The hwinfo.status() call takes around 2700ms on the GIGABYTE B650E AORUS ELITE X AX ICE motherboard.
Environment:
Motherboard: GIGABYTE B650E AORUS ELITE X AX ICE
hwinfo SDK Version: [8.12]
Additional Information:
I have tested this on multiple systems with the same motherboard and observed consistent results.
Other motherboards do not exhibit this behavior.