<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:blogger='http://schemas.google.com/blogger/2008' xmlns:georss='http://www.georss.org/georss' xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-4793880243486517617</id><updated>2024-08-29T17:57:43.725+09:00</updated><category term="ZFS"/><category term="httpd"/><title type='text'>Days of a mirror admin</title><subtitle type='html'>Various topics about a mirror server ftp.jaist.ac.jp very famous in Japan for  handling very heavy traffic.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://mirror-admin.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default?redirect=false'/><link rel='alternate' type='text/html' href='http://mirror-admin.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Kazuhiro Fujieda</name><uri>http://www.blogger.com/profile/14981573486598950760</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3fJy0iDz-Kuv08iH8mx-8yi5gXQYqvseS4_K2bfH6Zj3qQdJB1jN-brpHPJt_yiWTWYptl0-rNCj-A_yS2IDBgzCrXOTon6A2Pg7xsW1NMHvX9Yt8GJ6LPJtB0or5Jib55tXo7GookKnKbk6A7_WmyScHy9vOQigGKq1JuGhHv-Z8DQ/s220/%E9%A1%94%E3%82%A2%E3%82%A4%E3%82%B3%E3%83%B3%E5%B0%8F.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>4</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-4793880243486517617.post-7785424616176187479</id><published>2012-03-05T15:03:00.000+09:00</published><updated>2012-03-05T15:03:52.646+09:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="httpd"/><title type='text'>A brief test of Apache httpd 2.4.1</title><content type='html'>&lt;style&gt;
.http-stats table { border-style: solid; border-width: 1px; }
.http-stats td { border-style: solid; border-width: 1px; padding: 5px; }
.http-stats td.center { text-align: center; }
.http-stats td.right { text-align: right; }
&lt;/style&gt;
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.&lt;br&gt;
&lt;a href=&quot;http://mirror-admin.blogspot.com/2012/03/brief-test-of-apache-httpd-241.html#more&quot;&gt;Read more »&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://mirror-admin.blogspot.com/feeds/7785424616176187479/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://mirror-admin.blogspot.com/2012/03/brief-test-of-apache-httpd-241.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default/7785424616176187479'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default/7785424616176187479'/><link rel='alternate' type='text/html' href='http://mirror-admin.blogspot.com/2012/03/brief-test-of-apache-httpd-241.html' title='A brief test of Apache httpd 2.4.1'/><author><name>Kazuhiro Fujieda</name><uri>http://www.blogger.com/profile/14981573486598950760</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3fJy0iDz-Kuv08iH8mx-8yi5gXQYqvseS4_K2bfH6Zj3qQdJB1jN-brpHPJt_yiWTWYptl0-rNCj-A_yS2IDBgzCrXOTon6A2Pg7xsW1NMHvX9Yt8GJ6LPJtB0or5Jib55tXo7GookKnKbk6A7_WmyScHy9vOQigGKq1JuGhHv-Z8DQ/s220/%E9%A1%94%E3%82%A2%E3%82%A4%E3%82%B3%E3%83%B3%E5%B0%8F.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4793880243486517617.post-2009716615970423145</id><published>2011-12-07T10:34:00.000+09:00</published><updated>2012-03-01T11:30:41.071+09:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="ZFS"/><title type='text'>How to change the l2arc_write_max dynamically</title><content type='html'>ZFS sets the value of the &lt;span style=&quot;font-family: &amp;quot;Courier New&amp;quot;,Courier,monospace;&quot;&gt;l2arc_write_max&lt;/span&gt; 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.&lt;br&gt;
&lt;a href=&quot;http://mirror-admin.blogspot.com/2011/12/how-to-change-l2arcwritemax-dynamically.html#more&quot;&gt;Read more »&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://mirror-admin.blogspot.com/feeds/2009716615970423145/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://mirror-admin.blogspot.com/2011/12/how-to-change-l2arcwritemax-dynamically.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default/2009716615970423145'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default/2009716615970423145'/><link rel='alternate' type='text/html' href='http://mirror-admin.blogspot.com/2011/12/how-to-change-l2arcwritemax-dynamically.html' title='How to change the l2arc_write_max dynamically'/><author><name>Kazuhiro Fujieda</name><uri>http://www.blogger.com/profile/14981573486598950760</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3fJy0iDz-Kuv08iH8mx-8yi5gXQYqvseS4_K2bfH6Zj3qQdJB1jN-brpHPJt_yiWTWYptl0-rNCj-A_yS2IDBgzCrXOTon6A2Pg7xsW1NMHvX9Yt8GJ6LPJtB0or5Jib55tXo7GookKnKbk6A7_WmyScHy9vOQigGKq1JuGhHv-Z8DQ/s220/%E9%A1%94%E3%82%A2%E3%82%A4%E3%82%B3%E3%83%B3%E5%B0%8F.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4793880243486517617.post-4662062666428087765</id><published>2011-12-06T17:51:00.000+09:00</published><updated>2012-03-01T11:37:17.255+09:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="ZFS"/><title type='text'>How the L2ARC works</title><content type='html'>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&amp;#39;t cache dirty blocks in ARC written to HDDs. There is no data transfer between L2ARC and HDDs. When ZFS doesn&amp;#39;t cache a requested block in ARC but  L2ARC, it copy the block to ARC and respond it.&lt;br&gt;
&lt;br&gt;
&lt;div class=&quot;separator&quot; style=&quot;clear: both; margin: 0px; text-align: center;&quot;&gt;
&lt;a href=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnLTEomEpYPDygD02-CWrPe8ApocnPGuKEIRRHLN5Pg5xaMrq8emeSp-pb54VeUGKm5RCgAF58tH0d6kgHG0f8hA4Iw5y_2hSX3l4N24A0XCO80l814xWJ6CR2t7LC3qhgA7J8eDM5ZEia/s1600/L2ARC2.png&quot; imageanchor=&quot;1&quot;&gt;&lt;img border=&quot;0&quot; height=&quot;148&quot; src=&quot;https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnLTEomEpYPDygD02-CWrPe8ApocnPGuKEIRRHLN5Pg5xaMrq8emeSp-pb54VeUGKm5RCgAF58tH0d6kgHG0f8hA4Iw5y_2hSX3l4N24A0XCO80l814xWJ6CR2t7LC3qhgA7J8eDM5ZEia/s320/L2ARC2.png&quot; width=&quot;320&quot;&gt;&lt;/a&gt;&lt;/div&gt;
&lt;a href=&quot;http://mirror-admin.blogspot.com/2011/12/how-l2arc-works.html#more&quot;&gt;Read more »&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://mirror-admin.blogspot.com/feeds/4662062666428087765/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://mirror-admin.blogspot.com/2011/12/how-l2arc-works.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default/4662062666428087765'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default/4662062666428087765'/><link rel='alternate' type='text/html' href='http://mirror-admin.blogspot.com/2011/12/how-l2arc-works.html' title='How the L2ARC works'/><author><name>Kazuhiro Fujieda</name><uri>http://www.blogger.com/profile/14981573486598950760</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3fJy0iDz-Kuv08iH8mx-8yi5gXQYqvseS4_K2bfH6Zj3qQdJB1jN-brpHPJt_yiWTWYptl0-rNCj-A_yS2IDBgzCrXOTon6A2Pg7xsW1NMHvX9Yt8GJ6LPJtB0or5Jib55tXo7GookKnKbk6A7_WmyScHy9vOQigGKq1JuGhHv-Z8DQ/s220/%E9%A1%94%E3%82%A2%E3%82%A4%E3%82%B3%E3%83%B3%E5%B0%8F.jpg'/></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnLTEomEpYPDygD02-CWrPe8ApocnPGuKEIRRHLN5Pg5xaMrq8emeSp-pb54VeUGKm5RCgAF58tH0d6kgHG0f8hA4Iw5y_2hSX3l4N24A0XCO80l814xWJ6CR2t7LC3qhgA7J8eDM5ZEia/s72-c/L2ARC2.png" height="72" width="72"/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-4793880243486517617.post-1787302753265698285</id><published>2011-12-04T00:26:00.001+09:00</published><updated>2012-03-01T11:32:56.637+09:00</updated><category scheme="http://www.blogger.com/atom/ns#" term="ZFS"/><title type='text'>Higher l2arc_write_max is considered harmful</title><content type='html'>&lt;a href=&quot;http://storagetuning.wordpress.com/2011/12/01/zfs-tuning-for-ssds/&quot;&gt;This post&lt;/a&gt; is completely wrong. It shows how to tune L2ARC of ZFS as follows.&lt;br&gt;
&lt;ul&gt;
&lt;li&gt;Change the Record Size to a much lower value than 128 KB.&lt;/li&gt;
&lt;li&gt;Change the l2arc_write_max to a higher value.&lt;/li&gt;
&lt;li&gt; Set the l2arc_noprefetch=0.&lt;/li&gt;
&lt;/ul&gt;
All of them causes bad effects.
&lt;br&gt;
&lt;a href=&quot;http://mirror-admin.blogspot.com/2011/12/higher-l2arcwritemax-is-considered.html#more&quot;&gt;Read more »&lt;/a&gt;</content><link rel='replies' type='application/atom+xml' href='http://mirror-admin.blogspot.com/feeds/1787302753265698285/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://mirror-admin.blogspot.com/2011/12/higher-l2arcwritemax-is-considered.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default/1787302753265698285'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4793880243486517617/posts/default/1787302753265698285'/><link rel='alternate' type='text/html' href='http://mirror-admin.blogspot.com/2011/12/higher-l2arcwritemax-is-considered.html' title='Higher l2arc_write_max is considered harmful'/><author><name>Kazuhiro Fujieda</name><uri>http://www.blogger.com/profile/14981573486598950760</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='//blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh3fJy0iDz-Kuv08iH8mx-8yi5gXQYqvseS4_K2bfH6Zj3qQdJB1jN-brpHPJt_yiWTWYptl0-rNCj-A_yS2IDBgzCrXOTon6A2Pg7xsW1NMHvX9Yt8GJ6LPJtB0or5Jib55tXo7GookKnKbk6A7_WmyScHy9vOQigGKq1JuGhHv-Z8DQ/s220/%E9%A1%94%E3%82%A2%E3%82%A4%E3%82%B3%E3%83%B3%E5%B0%8F.jpg'/></author><thr:total>0</thr:total></entry></feed>