网站服务器(Php+IIS+Mysql) 出现访问缓慢的解决办法

最近网站服务器突然访问缓慢，重启网站服务器后正常，但过段时间又是这样

检查mysql数据库发现有不少数据的表出现需要修复的问题

TIME/TIMESTAMP/DATETIME columns of old format have...

检查mysql日志

Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-03-23T07:51:23.940552Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
2021-03-23T07:51:23.942401Z 0 [Note] InnoDB: Doublewrite buffer not found: creating new
2021-03-23T07:51:23.968803Z 0 [Note] InnoDB: Doublewrite buffer created
2021-03-23T07:51:23.988353Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2021-03-23T07:51:23.989083Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2021-03-23T07:51:23.990463Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
2021-03-23T07:51:23.999069Z 0 [Note] InnoDB: Foreign key constraint system tables created
2021-03-23T07:51:23.999741Z 0 [Note] InnoDB: Creating tablespace and datafile system tables.
2021-03-23T07:51:24.003861Z 0 [Note] InnoDB: Tablespace and datafile system tables created.
2021-03-23T07:51:24.004460Z 0 [Note] InnoDB: Creating sys_virtual system tables.
2021-03-23T07:51:24.009822Z 0 [Note] InnoDB: sys_virtual table created
2021-03-23T07:51:24.010429Z 0 [Note] InnoDB: Waiting for purge to start
2021-03-23T07:51:24.068569Z 0 [Note] InnoDB: 5.7.27 started; log sequence number 0
2021-03-23T07:51:24.070554Z 0 [Note] Plugin 'FEDERATED' is disabled.
2021-03-23T07:51:24.073783Z 0 [Warning] InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
mysqld: Table 'mysql.plugin' doesn't exist
2021-03-23T07:51:24.075985Z 0 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2021-03-23T07:51:24.077730Z 0 [Warning] InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
mysqld: Table 'mysql.gtid_executed' doesn't exist

mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=65536
max_used_connections=5
max_threads=1000
thread_count=5
connection_count=5
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 340379 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1a900996440
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
7ff66e7cb930    mysqld.exe!?has_stronger_or_equal_type@MDL_ticket@@QEBA_NW4enum_mdl_type@@@Z()
7ff66e7ce398    mysqld.exe!?upgrade_shared_lock@MDL_context@@QEAA_NPEAVMDL_ticket@@W4enum_mdl_type@@K@Z()
7ff66e87f298    mysqld.exe!?wait_while_table_is_used@@YA_NPEAVTHD@@PEAUTABLE@@W4ha_extra_function@@@Z()
7ff66e981518    mysqld.exe!?execute@Sql_cmd_shutdown@@UEAA_NPEAVTHD@@@Z()
7ff66e980850    mysqld.exe!?execute@Sql_cmd_repair_table@@UEAA_NPEAVTHD@@@Z()
7ff66e7d9367    mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@_N@Z()
7ff66e7dbc18    mysqld.exe!?mysql_parse@@YAXPEAVTHD@@PEAVParser_state@@@Z()
7ff66e7d4dd3    mysqld.exe!?dispatch_command@@YA_NPEAVTHD@@PEBTCOM_DATA@@W4enum_server_command@@@Z()
7ff66e7d5d4a    mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
7ff66e79ad6c    mysqld.exe!handle_connection()
7ff66f1e3772    mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff66eef417c    mysqld.exe!my_thread_once()
7ff894004f7f    MSVCR120.dll!_beginthreadex()
7ff894005126    MSVCR120.dll!_endthreadex()
7ff8aeef84d4    KERNEL32.DLL!BaseThreadInitThunk()
7ff8af391821    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1a900999540): REPAIR TABLE `met_admin_array`, `met_admin_column`, `met_admin_table`, `met_app`, `met_app_plugin`, `met_applist`, `met_column`, `met_config`, `met_cv`, `met_download`, `met_feedback`, `met_flash`, `met_flist`, `met_ifcolumn`, `met_ifcolumn_addfile`, `met_ifmember_left`, `met_img`, `met_infoprompt`, `met_job`, `met_label`, `met_lang`, `met_language`, `met_link`, `met_list` QUICK
Connection ID (thread ID): 70
Status: NOT_KILLED

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
2021-03-23T07:52:13.116579Z 0 [Warning] The use of InnoDB is mandatory since MySQL 5.7. The former options like '--innodb=0/1/OFF/ON' or '--skip-innodb' are ignored.
2021-03-23T07:52:13.116654Z 0 [Warning] option 'max_allowed_packet': unsigned value 2147483648 adjusted to 1073741824

如果使用phpmyadmin 选择所有错误的表进行Repair 修复，则mysql会突然崩溃，提示连不到mysql server 或mysql go away，需要手工再重启mysql才行

后只有逐个修复出错的表，单个逐个修复后正常