Scheduled Speedtests Templates

As for Network Performance Monitoring, the App is using templates to schedule speedtests. The speedtests are always executed between two agents so this is why we have two list. In the background, the systems will schedule speedtests between each agent of the first list with the agents on the second list.

For example, let say we have four agents: A, B, C and D.

By creating a template with A and B in the first list and C and D in the second list, the system will create four scheduled speedtests:

  • A-C
  • A-D
  • B-C
  • B-D

Speedtest Type (Mbps or Percent)

The scheduled speedtests can be configured with a limit to avoid congestion. The first limit is Mbps which is an absolute limit for the direction (from agent in 1st list to the agent in 2nd list and vice versa).

The second limit is a percent (%) of the Historical Maximum Speed of both agents. For example, if the percent is 50% in both directions and that the first agent historical Maximum Speed is 30 Mbps / 20 Mbps and the second agent is 100 Mbps / 100 Mbps, the speedtest will be executed at 50% of 30 Mbps (the lowest value between 30 Mbps and 100 Mbps) in one direction and 50% or 20 Mbps (the lowest value between 20 Mbps and 100 Mbps) in the other direction.

Frequency

The scheduled speedtests pre-set frequencies are:

  • Every hour
  • Every 2 hours
  • Every 3 hours
  • Every 4 hours
  • Every Day Between...
  • Custom (Advanced)

For all of them, the minute is randomized within the hour to make sure all speedtests are not executed at the same time. However, even if the minute is randomized, it is consistent between all the speedtest for a given agent pair. This means that if a speedtest is scheduled every hour between agent A and B, the speedtest could run the minute 23 but it will always run at the minute within each and every hour.

Timezone

The timezone for the scheduled speedtest is always UTC/GMT except for the Every Day Between option. In this case, the App will show the user timezone and convert automatically to UTC.

Custom (Advanced)

For users looking to customize the schedule, we support unix-like cron syntax. However, as explained previously in this article, the minute is ignore and randomize to distribute the tests during the hour. Also, the timezone is always UTC. Here are a few examples of what you could do with the advanced syntax:

  • Run every hour between 2am and 6am (UTC): 0 2-6 * * *  
  • Run at 4am (UTC) during weekend: 0 4 * * 6-7 

More details on the unix-like cron syntax on Wikipedia and test the syntax with Cron Tester.

Did this answer your question?