Consider these requirements to get the most from Wialon Local.

Web browser

Supported browsers are:

• Google Chrome
• Mozilla Firefox
• Opera
• Microsoft Edge

Computer capability

Computer capability affects browser operation. The key points of high performance are CPU (central processor) and RAM capacity. Multi-core processors do not affect browser operation in most cases. The exception is Google Chrome that can use more than one core in its operation.

Considering all the above mentioned, the minimum requirements are:

• CPU at 1,6 Hz clock rate;
• 512 MB of RAM.

and recommended requirements:

• CPU at 2,4 Hz clock rate
  (if Google Chrome is used as web browser, a processor with two and more cores is recommended);
• 2 GB of RAM.

Monitor size and screen resolution should be also considered. The bigger the monitor is, the more data is queried from server and processed by CPU. It is especially true for the maps and when the Internet connection is slow. The solution for big monitors is to not use browser in full-screen mode.

Antivirus software can slow down computer performance as well as gathering actual data from units. If Wialon Local is getting slower, you can add it to the list of exceptions or simply disable antivirus monitoring during Wialon Local session. You can also create a rule which allows Wialon Local to develop any activity.

Internet connection

Wialon Local requires 1 Mbit Internet connection channel for one computer. If more than one operator will work simultaneously, do some tests and choose the most appropriate speed.

Optimization measures

Here are some tips, which will help you to improve Wialon Local performance in cases when more than a hundred units are connected.

Web browser

Web browser is very important. See the list of supported browsers above. The most efficient is Google Chrome. It is followed by Mozilla Firefox and Opera. The slowest, according to our tests, is Internet Explorer.

Wialon Local efficiency strongly depends on browser event system. Each browser has its individual event model. As the tracking system is rather dynamic and tracks change with up to 2-second delay, some browsers (like Internet Explorer) cannot process such a large quantity of events. The solution here is to use a more powerful computer.

Graphics & tooltips

Graphic elements displayed on the map and in lists are resource-consuming. If you notice that your browser is getting slower, try to disable the mapping of the following elements: units, geofences, places, tracks, as well as names, direction arrows, and 'tails' for units (these elements are disabled with the three corresponding buttons in the Visible layers menu). Limit the number of units displayed in the Monitoring panel. Limit the number of other objects displayed on other panels that are frequently used (apply the filter for doing that). Enable only those elements that are necessary for your work at the moment. Several settings to adjust the way units are displayed are set in user settings in the Unit visualization on map section.

Unit's tooltip contents are also important. In the User settings dialog in the Show additional information about the unit section, you select which information should be presented in unit's tooltip and in extended unit information. To avoid browser overload, disable unusable items or even all items. If there are a lot of geofences or geofences composed of multiple points and the Presence in geofences option is enabled, then your browser could be strongly overloaded. So, make sure this option is disabled.

If the Internet connection is slow, disable geofences' rendering on map. Besides, if you query reports (containing map), messages, and tracks, clear your request as soon as it is no longer useful.

Pay attention to the fact that in order the charts to be shown the browser you use has to support the WebGL component. If the browser or the operating system cannot support it, you should enable the option Render charts on server in the user settings (limited functionality will be available).

Queries to server

When Wialon Local starts, not all data is loaded at once. It is made to speed up the loading and operation. That is why some action that done for the first time may take more time than for future work. Resource-consuming reports (such as reports on groups or reports with grouping and detalization) should be avoided. Enclosed rows of detalization stay hidden until you expand them, and if there are a hundred or more enclosed rows the browser may hang.