Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
req:req [14/06/2018 07:28]
irra [Limitations] WH-1
req:req [19/09/2018 12:26] (current)
tagr
Line 29: Line 29:
    * 2 GB of RAM.    * 2 GB of RAM.
  
-**Monitor size and screen resolution** should also be taken into account. The bigger the monitor is, the more data is queried from server and processed by CPU. For this reason the program may work perfectly on a 17-inch screen but start running slow on the 22-inch one. The solution for big monitors is not to use browser in a full-screen mode. This issue is especially actual at low speed of Internet connection.+**Monitor size and screen resolution** should also be taken into account. The bigger the monitor is, the more data is queried from the server and processed by CPU. For this reasonthe program may work perfectly on a 17-inch screen but start running slow on the 22-inch one. The solution for big monitors is not to use browser in a full-screen mode. This issue is especially actual at low speed of Internet connection.
  
 **Antivirus software** as well as gathering actual data from units can slow down computer performance. If Wialon is running 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 have any network activity. **Antivirus software** as well as gathering actual data from units can slow down computer performance. If Wialon is running 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 have any network activity.
Line 57: Line 57:
 A tooltip and additional information about the unit should also be taken care of. In the //Show additional information about the unit// section of the //​[[user/​set/​general#​show_additional_information_about_the_unit|User Settings]]//​ dialog, it is recommended to turn off the parameters that are not used (if necessary, switch off //all// the parameters). If there are a lot of geofences or geofences composed of multiple points and the //Presence in geofences// option is enabled, your browser can become overloaded. In such a case, make sure this option is disabled. ​ A tooltip and additional information about the unit should also be taken care of. In the //Show additional information about the unit// section of the //​[[user/​set/​general#​show_additional_information_about_the_unit|User Settings]]//​ dialog, it is recommended to turn off the parameters that are not used (if necessary, switch off //all// the parameters). If there are a lot of geofences or geofences composed of multiple points and the //Presence in geofences// option is enabled, your browser can become overloaded. In such a case, make sure this option is disabled. ​
  
-If the Internet connection is slow or you need to save the traffic, disable geofence rendering on the server. Besides, when you use reports with a map, messages, and tracksclear your request when it is no longer useful. ​+If the Internet connection is slow or you need to save the traffic, disable geofence rendering on the server. Besides, when you use reports with a map, messages, and tracks clear your request when it is no longer useful. ​
  
 Pay attention that in order for the charts to be displayed, the browser you use has to [[https://​get.webgl.org/​|support the WebGL component]]. If the browser or the operating system cannot support it, enable the //Render charts on server// option in the //​[[user/​set/​general#​obschie_nastrojki|User Settings]]//​ dialog (limited functionality will be available). Pay attention that in order for the charts to be displayed, the browser you use has to [[https://​get.webgl.org/​|support the WebGL component]]. If the browser or the operating system cannot support it, enable the //Render charts on server// option in the //​[[user/​set/​general#​obschie_nastrojki|User Settings]]//​ dialog (limited functionality will be available).
Line 63: Line 63:
 **3. Queries to Server** **3. Queries to Server**
  
-When Wialon starts, not all the data is loaded at once. It is made in order to speed up the loading and operation. That is why some actions that are performed for the first time may take more time than in the future. 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 freeze. ​ +When Wialon starts, not all the data is loaded at once. It is made in order to speed up the loading and operation. That is why some actions that are performed for the first time may take more time than in the future. 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 freeze.
- +
-===== Limitations ===== +
- +
-**Limits for logins and sessions:**  +
- +
-  * No more than 10 unsuccessful logins from one IP address per minute; +
-  * No more than 120 successful logins from one IP address per minute; +
-  * No more than 100 active sessions of one user from one IP address; +
-  * No more than 120 logins per minute. +
- +
-If these limits are met, IP address will be temporarily blocked. It can cause difficulty to log in to the system.  +
- +
-**Limits for messages:**  +
- +
-  * No more than 15 million messages can be loaded by a user from one IP address; +
-  * No more than 15 million messages can be loaded by a user from one IP address within 2 minutes; +
-  * No more than 500 thousand messages can be imported from one IP address per minute. +
- +
-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 //Tracks//, //​Messages//,​ and //Reports// panels (or simply reload the page) and try again.  +
- +
-**Limits for reports:**  +
- +
-  * Online execution of a report takes up to 2 minutes; +
-  * No more than 200 executions within 5 minutes by a user from one IP address; +
-  * The maximum number of lines of a report is 100000; +
-  * Report execution on jobs takes up to 10 minutes; +
-  * Report execution on notifications takes up to 5 minutes; +
-  * A user cannot execute in one hour the number of reports that is higher than the number the summary execution of which requires more than one hour.  +
- +
-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.).  +
- +
-**Limits for tracks:** +
- +
-  *During one session it is not possible to build more than 50 tracks in total in all panels (//Tracks, Monitoring, Reports, Messages//​). +
- +
-**Other limitations:​**  +
- +
-  * No more than 3 resource-intensive requests (e.g., message loading, report execution, etc.) can be processed simultaneously in a session; +
-  * No more than 10 API requests can be processed simultaneously during one session; +
-  * No more than 3 map tracings can be processed simultaneously during one session; +
-  * No more than 10 '​avl_evts'​ requests within one session can be processed within 10 seconds; +
-  * It is not possible to create in one resource more than 31744 [[sidebar/​start#​main_interface|micro objects]] of **each** type (geofences, jobs, notifications,​ drivers, trailers, passengers and report templates). ​  +
Follow us on Facebook Gurtam Wialon Twitter Gurtam Wialon info@gurtam.com   |   Copyright © 2002-2018 Gurtam