A brief test of Apache httpd 2.4.1

I briefly tested the Apache httpd 2.4.1 on ftp.jaist.ac.jp. I tested the worker MPM at first. The server, however, become increasingly slower to return responses not long after it started running. It finally stop returning any response. I gave up using the worker MPM. Then I tested the worker MPM. It consumed more memory and CPU than the version 2.2.22.

How to change the l2arc_write_max dynamically

ZFS sets the value of the l2arc_write_max to the each cache device of L2ARC only when you add it to a pool of ZFS or restart the OS. If you want to change the value dynamically, you should follow the following steps with the mdb.

How the L2ARC works

L2ARC of ZFS is quite different from an ordinary L2 cache of a CPU. The following figure shows the structure of the caches of ZFS. L2ARC caches only blocks in the ARC read from HDDs. It doesn't cache dirty blocks in ARC written to HDDs. There is no data transfer between L2ARC and HDDs. When ZFS doesn't cache a requested block in ARC but  L2ARC, it copy the block to ARC and respond it.

Higher l2arc_write_max is considered harmful

This post is completely wrong. It shows how to tune L2ARC of ZFS as follows.

• Change the Record Size to a much lower value than 128 KB.
• Change the l2arc_write_max to a higher value.
• Set the l2arc_noprefetch=0.

All of them causes bad effects.