mirror of
https://github.com/nextcloud/documentation.git
synced 2025-10-26 11:18:02 +00:00
performance.rst: fix "slow_query_log_file" configuration
This commit is contained in:
parent
e12cd18ee0
commit
dedc27b8a9
@ -30,7 +30,7 @@ With MySQL it is very easy with just a bit of configuration:
|
||||
If you put this into your my.cnf file, every query that takes longer than one second is logged to a logfile::
|
||||
|
||||
slow_query_log = 1
|
||||
slow_query_log = /var/log/mysql/mysql-slow.log
|
||||
slow_query_log_file = /var/log/mysql/mysql-slow.log
|
||||
long_query_time=1
|
||||
|
||||
If a query takes more than a second we have a serious problem of course. You can watch it with `tail -f /var/log/mysql/mysql-slow.log` while using Nextcloud.
|
||||
@ -40,7 +40,7 @@ If a query takes more than a second we have a serious problem of course. You can
|
||||
If you reduce the long_query_time to zero then every statement is logged. This is super helpful to see what is going on. Just do a `tail -f` on the logfile and click around in the interface or access the WebDAV interface::
|
||||
|
||||
slow_query_log = 1
|
||||
slow_query_log = /var/log/mysql/mysql-slow.log
|
||||
slow_query_log_file = /var/log/mysql/mysql-slow.log
|
||||
long_query_time=0
|
||||
|
||||
3. log queries without an index.
|
||||
@ -49,7 +49,7 @@ If you increase the long_query_time to 100 and add log-queries-not-using-indexes
|
||||
|
||||
log-queries-not-using-indexes
|
||||
slow_query_log = 1
|
||||
slow_query_log = /var/log/mysql/mysql-slow.log
|
||||
slow_query_log_file = /var/log/mysql/mysql-slow.log
|
||||
long_query_time=100
|
||||
|
||||
Measuring performance
|
||||
|
||||
Loading…
Reference in New Issue
Block a user