<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000'><div class="titlepage"><div><div><h3 class="title"><span style="font-weight: normal;">Maybe from here?</span><br></h3><h3 class="title"><span style="font-weight: normal;">https://fs.hlrs.de/projects/craydoc/docs/books/S-0010-31/html-S-0010-31/z1112312952ebishop.html</span><br></h3><h3 class="title">3.3.6 Disabling OSS Read Cache and Writethrough Cache</h3></div></div></div>
<p>Lustre uses the Linux page cache to provide read-only caching of data
on object storage servers (OSS). This strategy reduces disk access time
caused by repeated reads from an OST. OSS read cache is enabled by
default, but you can disable it by setting <code class="filename">/proc</code> parameters. For example, invoke the following on the OSS:</p>
<pre class="screen" style="background-color: rgb(224, 224, 224);">nid00008:~ # <strong class="userinput"><code>lctl set_param obdfilter.*.read_cache_enable 0</code></strong></pre>
<p>Writethrough cache can also be disabled. This prevents file writes
from ending up in the read cache. To disable writethrough cache, invoke
the following on the OSS:</p>
<pre class="screen" style="background-color: rgb(224, 224, 224);">nid00008:~ # <strong class="userinput"><code>lctl set_param obdfilter.*.writethrough_cache_enable 0</code></strong></pre><br><br><hr id="zwchr"><div style="color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Mark Day" <mark.day@rsp.com.au><br><b>To: </b>"Mohr Jr, Richard Frank (Rick Mohr)" <rmohr@utk.edu><br><b>Cc: </b>lustre-discuss@lists.lustre.org<br><b>Sent: </b>Saturday, 8 December, 2012 10:52:28 AM<br><b>Subject: </b>Re: [Lustre-discuss] noatime or atime_diff for Lustre 1.8.7?<br><br><style>p { margin: 0; }</style><div style="font-family: trebuchet ms,sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">> 2) Make sure caching is enabled on the oss.<br><br>How do you check/enable for this? Is it not enabled by default?<br><br>Cheers, Mark<br><br><hr id="zwchr"><div style="color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Mohr Jr, Richard Frank (Rick Mohr)" <rmohr@utk.edu><br><b>To: </b>"Grigory Shamov" <gas5x@yahoo.com><br><b>Cc: </b>lustre-discuss@lists.lustre.org<br><b>Sent: </b>Saturday, 8 December, 2012 5:19:31 AM<br><b>Subject: </b>Re: [Lustre-discuss] noatime or atime_diff for Lustre 1.8.7?<br><br>On Dec 6, 2012, at 2:58 PM, Grigory Shamov wrote:<br><br>> So, on one of our OSS servers the load is now 160. According to collectl, only one OST does most of the job. (We dont do striping on this FS; unless users to it manually on their subdirectories).<br><br>This sounds similar to situations we see every now and then. The load on the oss server climbs until it is roughly equally to the number of oss threads (which sounds like your case with load=oss_threads=160), but only a single ost is performing any significant IO. This seems to arise when parallel jobs access the same file which has stripe_count=1. The oss is bombarded with so many requests to a single ost that they backlog and tie up all the oss threads. At that point, all IO to the oss slows to a crawl no matter which ost on the oss is being used. This becomes problematic because even a modest sized job can effectively DOS and oss server.<br><br>When you encounter these problems, is the IO to the affected ost primarly one-way (ie - mostly reads or mostly writes)? In our cases, we tend to see this when parallel jobs are reading from a common file. There are a couple of things that I have found that help:<br><br>1) Increase the file striping a lot. This helps spread the load over more osts. We have had success with striping even relatively small files (~10 GB) over 100+ osts. Not only does it reduce load on the oss, but it usually speeds up the application significantly.<br><br>2) Make sure caching is enabled on the oss. For us, this seems to help mostly when lots of processes are reading in the same file.<br><br>Not sure if your situation is exactly like what I have seen, but maybe some of that info can help a bit.<br><br>-- <br>Rick Mohr<br>Senior HPC System Administrator<br>National Institute for Computational Sciences<br>http://www.nics.tennessee.edu<br><br><br>_______________________________________________<br>Lustre-discuss mailing list<br>Lustre-discuss@lists.lustre.org<br>http://lists.lustre.org/mailman/listinfo/lustre-discuss<br></div><br></div><br>_______________________________________________<br>Lustre-discuss mailing list<br>Lustre-discuss@lists.lustre.org<br>http://lists.lustre.org/mailman/listinfo/lustre-discuss<br></div><br></div></body></html>