Question 1

What is the AppLatency check mark in the HMap button menu responsible for in the MoonBot terminal?

Kost · Accepted Answer

In the MoonBot terminal, when you right-click on the HMap (heat map of orders) button, a window opens in which you can check the AppLatency parameter, after that, in the window of the heat map of orders, instead of orders, the AppLatency diagnostic graph will be displayed with green dots, which conditionally shows how much the application itself slows down, the flow synchronization time is ideally up to 16 milliseconds (timer accuracy on VDS), normally up to 100 milliseconds. When you move the cursor vertically along this graph, the letter "A:" will be displayed on the left of the cursor line with delay data in milliseconds (from A:0 and more). You can enlarge the graph vertically using the Heigh slider in the HMap window, and you can stretch or shrink the graph horizontally using the mouse wheel. After operational monitoring of this data, you can uncheck the AppLatency parameter again and the heat map with orders will be displayed in this window again.

Question 2

What is the AppLatency check mark in the HMap button menu responsible for in the MoonBot terminal?

Kost · Accepted Answer

In the MoonBot terminal, when you right-click on the HMap (heat map of orders) button, a window opens in which you can check the AppLatency parameter, after that, in the window of the heat map of orders, instead of orders, the AppLatency diagnostic graph will be displayed with green dots, which conditionally shows how much the application itself slows down, the flow synchronization time is ideally up to 16 milliseconds (timer accuracy on VDS), normally up to 100 milliseconds. When you move the cursor vertically along this graph, the letter "A:" will be displayed on the left of the cursor line with delay data in milliseconds (from A:0 and more). You can enlarge the graph vertically using the Heigh slider in the HMap window, and you can stretch or shrink the graph horizontally using the mouse wheel. After operational monitoring of this data, you can uncheck the AppLatency parameter again and the heat map with orders will be displayed in this window again.