I notice that my first upload sync with nextcloud was having some issues… would get alot of long pauses before it would start back up again… uploaded a total of 140gbs… Now with owncloud I never had this upload issuess… Strange thing is I really didn’t get any errors… I got a fetal webdav error and another php error but i think that happened when I forced closed the desktop app… Everything did upload but it took 3x as long as owncloud used to. Now two things I did afterwards… I changed the php memory limit to 768 and I dropped the strict-Transport-Security from 31536000 to the recommended size of 15768000 but not being an expert I am not sure any of that did anything. But in phpMyAdmin in the adviser I am getting a lot of suggestions and was wondering if I should be concerned about any of them… Would be helpful if anyone knows if I should be taking any of these suggestions seriously…
I am on mysql 5.7…
The query cache is not enabled —
The query cache is known to greatly improve performance if configured correctly. Enable it by setting query_cache_size to a 2 digit MiB value and setting query_cache_type to ‘ON’. Note: If you are using memcached, ignore this recommendation.
There are too many joins without indexes.
This means that joins are doing full table scans. Adding indexes for the columns being used in the join conditions will greatly speed up table joins.
The rate of reading the first index entry is high.
This usually indicates frequent full index scans. Full index scans are faster than table scans but require lots of CPU cycles in big tables, if those tables that have or had high volumes of UPDATEs and DELETEs, running ‘OPTIMIZE TABLE’ might reduce the amount of and/or speed up full index scans. Other than that full index scans can only be reduced by rewriting queries.
The rate of reading data from a fixed position is high.
This indicates that many queries need to sort results and/or do a full table scan, including join queries that do not use indexes. Add indexes where applicable.
The rate of reading the next table row is high.
This indicates that many queries are doing full table scans. Add indexes where applicable.
MyISAM key buffer (index cache) % used is low.
You may need to decrease the size of key_buffer_size, re-examine your tables to see if indexes have been removed, or examine queries and expectations about what indexes are being used.
The % of indexes that use the MyISAM key buffer is low.
You may need to increase key_buffer_size.
The rate of opening tables is high.
Opening tables requires disk I/O which is costly. Increasing table_open_cache might avoid this.