Quote:
Originally Posted by qasdfdsaq
Because you get turned on by it.
|
I get turned on by you, big boy*
*statement isn't necessarily true
Anyway, as promised here are a few graphs showing VMNG300, R30 and R36 figures.
Reactivated superhub on R30, waiting for the new firmware, you can see right before the end of the graph the red spike and drop in latency when R36 was applied. After that it went into modem mode.
As you can see below, in modem mode i wasn't happy with the performance of the hub, so i spent the next little while trying to switch upstreams to see if that was the cause of the jitter i was receiving. Up till 4am is the VMNG300, after 4PM is the hub in router mode running R36.
and again on the 26th i switched upstreams again in modem mode from one to the other, no chance at all, very poor.
Suffice to say the majority of the time i've been in router mode, where i've been receiving good (for VM) service. The morning is router mode, the red block is me switching to modem mode, as the router mode decided it wasn't playing nice... but i returned to router mode and onto the less congested upstream as you can see here
And ever since then, i've had the following "good for VM" service
^^ R36 in combo (router) mode, with jitter between 0 and 2 on a more or less constant basis, flicks between 0 and 1 most of the time.
for comparison, VMNG300 before reactivation of SH, which for some reason went from this...
to this...
Either way, imho, R36 = good for the SH, lets just hope they continually improve it further and dont introduce more bugs.