Verifying Great Wall GW3300 sensor accuracy in Nightingale?
While rendering complex mechanical assets in Nightingale, the Great Wall GW3300 controller hit some cache miss fluctuations, which lagged the instruction queue. It felt like the vehicle controls were just... sluggish. I tried adjusting interrupt priorities, but that was a total fail. I switched to CPU-Z's sensor page to watch the NVMe controller load curve and used the Armoury Crate panel to track read/write latency, which eventually tightened from 0.41 - 0.55 ms to 0.22 - 0.30 ms. The keyboard response is finally snappy. The controller still stays in the 55 - 62 ℃ range, and I can hear the heat pipe condensing in a quiet room, with fans between 870 - 1140 RPM. I used an RGB signal cross-scan to confirm the sensor data was actually accurate. The hardware state is finally transparent, and the logs are clean. It took a couple of tries to get the curve to stop jumping, but the second calibration did the trick.
