Manual:Tools/Speed Test: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
mNo edit summary
Line 58: Line 58:
==Usage example==
==Usage example==


Bandwidth and speed tests should be done through the link or device under test (DUT) on powerful devices to ensure that DUT CPU is not the bottleneck due to traffic generating process.
Bandwidth and speed tests should be conducted through the devices, not on them to ensure real life simulation and not to overload the CPU on the devices under testing,(DUT) due to traffic generating process.


To run simple test from device A (192.168.88.1) to device B (192.168.88.2)
To run a simple test from device A (192.168.88.1) to device B (192.168.88.2):
<pre>
<pre>
[admin@MikroTik]] > /tool speed-test address=192.168.88.1
[admin@MikroTik]] > /tool speed-test address=192.168.88.1

Revision as of 15:19, 29 November 2018

Applies to RouterOS: v6.44beta39+

Summary

Sub-menu: /tool
Packages required: system


The Speed Test is an easy test tool for measuring ping, jitter, TCP and UDP throughput from one MikroTik device, to another.
"speed-test" command is based on Ping Tool and Bandwidth Test.

General interface properties

Sub-menu: /tool speed-test

address (IP address; Default: "") IP address of host
connection-count (integer; Default: 20) If device has more than 20 cores - core count will be used
password (string; Default: ) Password for the remote device
test-duration (integer; Default: 10) Duration for each test
user (string; Default: admin) Remote device username


Usage example

Bandwidth and speed tests should be conducted through the devices, not on them to ensure real life simulation and not to overload the CPU on the devices under testing,(DUT) due to traffic generating process.

To run a simple test from device A (192.168.88.1) to device B (192.168.88.2):

[admin@MikroTik]] > /tool speed-test address=192.168.88.1
              status: done
      time-remaining: 0s
    ping-min-avg-max: 541us / 609us / 3.35ms
  jitter-min-avg-max: 0s / 76us / 2.76ms
                loss: 0% (0/100)
        tcp-download: 921Mbps local-cpu-load:30%
          tcp-upload: 920Mbps local-cpu-load:30% remote-cpu-load:25%
        udp-download: 917Mbps local-cpu-load:6% remote-cpu-load:21%
          udp-upload: 916Mbps local-cpu-load:20% remote-cpu-load:6%

If any of device CPU utilization during test reaches 100% warning message will appear:

[admin@MikroTik]] > /tool speed-test address=192.168.88.1
                  ;;; results can be limited by cpu, note that traffic generation/termination 
                      performance might not be representative of forwarding performance
              status: done
      time-remaining: 0s
    ping-min-avg-max: 541us / 609us / 3.35ms
  jitter-min-avg-max: 0s / 76us / 2.76ms
                loss: 0% (0/100)
        tcp-download: 721Mbps local-cpu-load:78%
          tcp-upload: 820Mbps local-cpu-load:100% remote-cpu-load:84%
        udp-download: 906Mbps local-cpu-load:10% remote-cpu-load:54%
          udp-upload: 895Mbps local-cpu-load:55% remote-cpu-load:12%

"test-duration" parameter allows changing duration of all of the 5 tests:

  • ) Ping test with 50ms delay
  • ) TCP recieve
  • ) TCP send
  • ) UDP recieve
  • ) UDP send

[ Top | Back to Content ]