This article mainly introduces how to handle the phpinclude file timeout issue. For more information, see the recent findings that php always Times out when automatically loading class functions and tracks php slow query logs, it is found that the program timed out when it is stuck in a class file of include.
Initially, I/O response times out, and hard disk reading is faulty.
Use several commands to locate the problem:
Iostat-d-x-k 1 10 // run 10 times to check that the wait parameter in iostat is very large, generally no more than 5 ms. the closer the two parameters of await svctm are, better io performance.
Refer to other blogs,
Await: Average time (in milliseconds) for processing each IO request ). It can be understood as the IO response time. Generally, the system IO response time should be less than 5 ms. if it is greater than 10 ms, it will be relatively large.
This time includes the queue time and service time. that is to say, in general, await is larger than svctm, and the smaller the difference, the shorter the queue time, and the larger the difference, the longer the queue time, it indicates a problem with the system. Svctm indicates the average service time (in milliseconds) for each device I/O operation ). If the svctm value is very close to await, it indicates that there is almost no I/O wait, and the disk performance is good. if The await value is much higher than the svctm value, the I/O queue waits too long, and applications running on the system will slow down.
Sudo iotop-o, // view the program on the hard disk and check the io usage of the process.
Sudo perf top // view the process io usage
Sudo hdparm-t/dev/***** View disk read efficiency
Display: Timing buffered disk reads: 10 MB in 3.14 seconds = 3.18 MB/sec
View non-interrupted sleep
While true; do date; ps auxf | awk '{if ($8 = "D") print $0 ;}'; sleep 1; done
After tracking through the above command, the hard disk reading efficiency is very low, further reasons are unknown, it may be that the hard disk has a bad track.