Quote:
Originally Posted by mike86
Why did the graph change immediately after switching to the SH3? Is it the Hub itself that's treating it as low priority traffic?
|
Although I've asked behind the scenes about that, VM have never graced me with an answer. Modem mode is indeed the acid test when comparing SH2ac with the Hub 3 since it is the router that is responding to the pings. Ergo, the high maxima shown in the BQM must be something the modem is doing.
One theory advanced by Legacy1 in the VM forums is that the Intel-ATOM processor within the Puma-6 package goes into a sleep state via ACPI. It's logical but unlikely because the CPU, unless totally misconfigured, would not get the chance to go to sleep.
The other theory is that at low level, there is diagnostic code running in the Hub 3. We saw something like that in the early SH2 and SH2 days.
One needs to bear in mind that it is the average latency that matters (the blkue line). You could have just one spike in a BQM window, and that accounts for the yellow portion. If latency was high all the time, then the avergae latency would reflect that.