|max_execution_time||How many CPU-seconds a script can consume||30|
|max_input_time||How long (seconds) a script can wait for input data||60|
|memory_limit||How much memory (bytes) a script can consume before being killed||32M|
|output_buffering||How much data (bytes) to buffer before sending out to the client||4096|
These numbers depend mostly on your application. If you accept large files from users, then
max_input_time may have to be increased, either in php.ini or by overriding it in code. Similarly, a CPU- or memory-heavy program may need larger settings. The purpose is to mitigate the effect of a runaway program, so disabling these settings globally isn’t recommended. Another note on
max_execution_time: This refers to the CPU time of the process, not the absolute time. Thus a program that does lots of I/O and few calculations may run for much longer than
max_execution_time. It’s also how
max_input_time can be greater than
The amount of logging that PHP can do is configurable. In a production environment, disabling all but the most critical logs saves disk writes. If logs are needed to troubleshoot a problem, you can turn up logging as needed.
error_reporting = E_COMPILE_ERROR|E_ERROR|E_CORE_ERROR turns on enough logging to spot problems but eliminates a lot of chatter from scripts.