diff options
author | Thomas Steur <tsteur@users.noreply.github.com> | 2020-06-21 15:42:06 +0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-06-21 15:42:06 +0300 |
commit | 77f607d49fb632a87c53c3513a2f5fcf7c66a185 (patch) | |
tree | 86efa169c5b0d1a06466e7cd91af968f84d403a3 /config | |
parent | 27842d7de0fa8ae248cf1ef31660994ba5569b4f (diff) |
Allow configuration of a shorter lock wait time in tracker mode (#16092)
* Allow configuration of a shorter lock wait time in tracker mode
* do not catch errors for single tracking request
* Update global.ini.php
Diffstat (limited to 'config')
-rwxr-xr-x | config/global.ini.php | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/config/global.ini.php b/config/global.ini.php index c3c628bbd3..81535c8eaf 100755 --- a/config/global.ini.php +++ b/config/global.ini.php @@ -886,6 +886,14 @@ enable_sql_profiler = 0 ; Enables using referrer spam blacklist. enable_spam_filter = 1 +; If a value greater than 0 is configured, Matomo will configure MySQL with the set lock wait timeout in seconds during a +; tracking request. This can be useful if you have a high concurrency load on your server and want to reduce the time of +; lock wait times. For example configuring a value of 3-10 seconds may give your Matomo a performance boost if you have +; many concurrent tracking requests for the same visitor. When enabling this feature, make sure the MySQL +; variable "innodb_rollback_on_timeout" is turned off. Only configure if really needed. The lower the value the more tracking +; requests may be discarded due to too low lock wait time. +innodb_lock_wait_timeout = 0 + [Segments] ; Reports with segmentation in API requests are processed in real time. ; On high traffic websites it is recommended to pre-process the data |