Consider these requirements to get the most from Wialon.
Supported browsers are:
If you use a browser not mentioned above, Wialon may function incorrectly.
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 above mentioned, the minimum requirements are:
and recommended requirements:
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 is getting slower, you can add it to the list of exceptions or simply disable antivirus monitoring during Wialon session. You can also create a rule which allows Wialon to develop any activity.
Wialon 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.
Furthermore, when working with Wialon, your IP address should not be changed within a session.
Here are some tips, which will help you to improve Wialon performance in cases when more than a hundred units are connected.
1. 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 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.
2. 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 bottom panel. 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 section 'Unit visualization on map'.
Unit's tooltip contents are also important. In User Settings dialog in the section 'Show additional information about the unit', 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 option 'Presence in geofences' is enabled, then your browser could be strongly overloaded. So, make sure this option is disabled.
If 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.
3. Queries to Server
When Wialon 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 is a hundred or more enclosed rows the browser may hang.
Limits for logins and sessions:
If these limits are met, IP address will be temporarily blocked. It can cause difficulty to log in to the system.
Limits for messages:
If these limits are met, messages stop being loaded or imported. It may cause difficulties in executing reports, building tracks, etc. If this happens, you can clear the panels Tracks, Messages, and Reports (or simply reload the page) and try again.
Limits for reports:
When the timeout is exceeded, report execution will be aborted. That means the report will not be generated. In this case, diminish time interval, number of analyzed objects, or scope of requested data (tables, charts, etc.).