What affects performance by causing a large Apache access.log?

If a log file, such as access.log or error.log, becomes very large, will a large issue affect Apache performance or user access? In my opinion, Apache does not read entire logs in memory, but simply uses filehandle for writing. Correctly? If so, I do not need to delete the logs manually every time it is large enough, except for a file system problem. Please help and correct me if I am wrong. Or is there an Apache log I / O issue I have to take care of when starting up?

thank you very much

+3
source share
1 answer

, . apache . , , . , , .

, , .

- apche.

, , . 1 10000 . , , . , Apache , . , , .

Apache Software Foundation

+1

All Articles